>Not sure if your suggestion is aimed at me Yes :) The package can probably be updated, but the bug report will need some additional details first.
I understand some of the concepts can be confusing. I've written a short overview to explain some terms. At its core, Ubuntu is based on the same packages as Debian, though some may have additional Ubuntu-only changes. This means that most newer versions first land in Debian (Sid) and then make their way into the development version of Ubuntu (currently Hirsute) In the case where Debian has packaged a newer version, the version numbers may look something like this: Debian: 1.1 Ubuntu: 1.0 In this case Ubuntu will see that Debian has a newer version and update to it, so that Ubuntu also includes 1.1. This is what is known as a sync, which is taking a package from Debian and adding it to the archive. For the majority of the development cycle this is done automatically, but as the release approaches need to be requested manually as mentioned earlier. So that's the easy case. For other packages, Ubuntu has added some patches either fixing issues (sometimes this takes shorter time than waiting for an update from Debian) or branding or something Ubuntu-specific: Debian: 1.1 Ubuntu: 1.0ubuntu1 This is where it gets tricky, because you cannot tell by the version number alone if version 1.1 contains all the necessary changes in 1.0ubuntu1. These are not synced automatically. A human needs to look at the new version and decide if the Ubuntu changes are still needed. If they are, a new package is prepared with the new changes from Debian AND the changes in Ubuntu, typically resulting in 1.1ubuntu1. This is known as a merge, because the changes are merged together. Alternativly, if the Ubuntu-changes can be dropped (often because Debian has included the fixes in the new version) the package can be synced. You can always tell if a package has additional Ubuntu-changes and a merge might be required if the version number contains "ubuntu". Since the existing Ubuntu-changes prevents an automatic sync, the package won't be updated until someone has checked whether it needs to be merged or synced depending on what the new version contains. An upload is basically when you add a new version of a package you have prepared. This requires special permissions, but the rest of us can request it by subscribing the ubuntu-sponsors team and they can do it for you. Let me know if things are still unclear :) With that in place, let's look at this again >An explicit sync is not necessary, when > we're before DebianImportFreeze (check ReleaseSchedule) and > our version of the package has no Ubuntu changes > and the Debian package is in sid (in testing for LTS releases of Ubuntu) As you mention, the package is in Sid and Hirsute is not currently in Freeze, so thats good. However, 22~exp1ubuntu4 means the packages does contain Ubuntu changes so as in the general case above we need to know whether it should be merge or if it can simply be synced. Luckily, comment #2 did the checking and concluded the Ubuntu changes are no longer needed, therefore it can be synced. The remaining part is updating the bug report with some details (take a look at the bullet points under "Content of a sync request" and subscribing ubuntu-sponsors since they are the ones who need to push the "sync"-button in order to pull in the new version. Also, the `syncpackage` tool is used by the sponsors, so I don't know how it works. You can take a look at `requestsync` which shows a template for requesting syncs and allow you to read through it and make changes before deciding whether to submit it or not :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897394 Title: Please sync gcc-mingw-w64-x86-64 (10.1.0-3+23) from debian Bullseye To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-mingw-w64/+bug/1897394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
