Hello larsen, or anyone else affected, Accepted apt into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.23 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 and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. 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 Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-trusty -- 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/1821308 Title: apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22 Status in apt package in Ubuntu: Invalid Status in apt source package in Trusty: Fix Committed Bug description: [Impact] Pinning on local-only package versions is ignored, causing them to be upgraded. [Test case] The integration tests run in autopkgtest include an automated test case that contains a package called coolstuff in three versions. We are specifying a Pin for the installed one, set to 1000. The bug caused 1.0 to become the candidate, as the existing pin was ignored. The test checks that 2.0~bpo1 to remains the candidate, that is, apt-cache policy looks like this: coolstuff: Installed: 2.0~bpo1 Candidate: 2.0~bpo1 Package pin: 2.0~bpo1 Version table: 2.0~bpo2 1000 100 file:${tmppath}/aptarchive/ backports/main i386 Packages *** 2.0~bpo1 1000 100 ${tmppath}/rootdir/var/lib/dpkg/status 1.0 1000 500 file:${tmppath}/aptarchive/ stable/main i386 Packages On the output of the autopkgtest we'll see: Check that local-only versions can be pinned correctly (LP: #1821308) Test for successful execution of apt-cache policy coolstuff … PASS Test for correctness of file testsuccess.output … PASS [Regression potential] Other weird pinning bugs. [Original bug report] I have updated apt this morning: Start-Date: 2019-03-22 09:36:18 Commandline: apt-get dist-upgrade Upgrade: apt:amd64 (1.0.1ubuntu2.20, 1.0.1ubuntu2.22), ... Afterwards, apt-get ignores my pinning preferences: # apt-get --dry-run upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be DOWNGRADED: burp 0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded. Inst burp [2.0.54-1] (1.3.48-4 Ubuntu:14.04/trusty [amd64]) Conf burp (1.3.48-4 Ubuntu:14.04/trusty [amd64]) # cat /etc/apt/preferences.d/burp.pref Package: burp Pin: version 2.0.54* Pin-Priority: 1000 This might be caused by bug 1814727 as it's the only thing I can see in the changelog regarding apt/pinning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821308/+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
