On IRC, emorrp1 pointed a mistake I made: the NMU is included in the current git history, after the packaging of the new upstream version. I only missed it because for some reason "7 months ago" sounded older than the 64-bit time_t transition. This made me look around a bit more, and I noticed there is a dedicated upstream branch for fixing OpenMW with the latest MyGUI: https://gitlab.com/OpenMW/openmw/-/merge_requests/3319 I still think it would be worth reorganizing the current MyGUI git history, from: 1. current unstable version (minus the NMU) 2. 3.4.2 fix (allowing OpenMW to be usable) 3. 3.4.3 new upstream version (breaking OpenMW unless it is patched) 4. NMU import 5. some fixes to 3.4.3 to: 1. current unstable version (minus the NMU) 2. NMU import 3. 3.4.2 fix (allowing OpenMW to be usable) 4. 3.4.3 new upstream version (breaking OpenMW unless it is patched) 5. some fixes to 3.4.3 This would allow to upload first the step 3. (current unstable + NMU + 3.4.2 fix), then have more time to import the OpenMW branch fixing its compatibility with MyGUI 3.4.3, to finally upload MyGUI 3.4.3 and the patched OpenMW at the same time. I am obviously still opened to feedback, and will not touch anything outside of a dedicated new branch until I get some confirmation that this reorganization is indeed going to help getting the updated MyGUI into unstable. --- Bret, if you’re reading this, I’m not trying nor planning to take over anything, and as the usual maintainer you obviously get the final word. My motivation here is to fix OpenMW in Debian unstable, and I was under the impression that the process is stuck since all fixes are ready in Salsa but never got uploaded. If I missed a reason why this has not been uploaded yet, please tell me about it and I’ll try to help with that instead.
Attachment:
pgpHm7mgkkMOp.pgp
Description: Signature digitale OpenPGP