Hello Julian, or anyone else affected, Accepted apt into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.1.10ubuntu0.3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Groovy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1918920 Title: Harden test for no new acquires after transaction abort Status in apt package in Ubuntu: Fix Committed Status in apt source package in Bionic: New Status in apt source package in Focal: New Status in apt source package in Groovy: Fix Committed Bug description: [Impact] test-pdiff-usage is somewhat flaky, especially on Debian, this makes it less flaky. No end user impact as it's a test-only change. [Test plan] Running autopkgtest, which runs our extensive integration test suite which includes the changed test. [Where problems could occur] No end user regression potential on its own, but might slightly change regression potential for future pdiff changes: Test approach is slightly different now. It still catches that updates fail correctly, but tests more concretely that a transaction was aborted rather than that no worker received work (which was not guaranteed, the work could be scheduled before it was aborted). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918920/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp