On Fri Mar 27 13:56:49 2026 +0000, Craig Schulstad wrote:
Alfred, I will direct this query and comment to you. Since my original project seemed to be getting convoluted, I decided to delete the project a couple of weeks ago and start from scratch. After the seven-day wait period, ensuring that the previous project was gone, I created a new project with a similar name, applied a new version of my language enhancement which included insulating the language subfolder search function to address the library load attempt per your suggestion. After that, and running a merge request, the enhancement passed all of the tests, which was progress. However, that pipeline never appeared to get anyone assigned to review it, and now the pipeline appears to be outdated. When reviewing the pipeline, it indicates that a "rebase" should be run, but I am a bit hesitant due to the warning message it gives me. The warning message says that if I am unsure, I should have a project maintainer review. So if either you or someone you know can review this pipeline before running a "rebase", I would appreciate it. FYI, the pipeline is "60289" and the project name is "wine_mui_NoDakker". Thanks in advance. Regards, Craig Convoluted indeed. I don't know what you did to that poor repo.
Pipeline https://gitlab.winehq.org/wine/wine/-/pipelines/60289 looks successful to me. I'm not seeing any warnings or unusual rebase-related messages, all I'm seeing is a successful rebase. If you mean "Fast forward merge is not possible. Please rebase." in https://gitlab.winehq.org/wine/wine/-/merge_requests/10365, ignore that. It reappears every day, whenever the main branch updates. Whoever merges it will rebase; if there's an actual merge conflict, the message will change. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10209#note_134073