[Bug 2029268] Please test proposed package

[Andreas Hasenack]

Hello Julian, or anyone else affected,

Accepted apt into lunar-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.6.0ubuntu0.1 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-
lunar to verification-done-lunar. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-lunar. 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 Jammy)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2029268

Title:
  Do not consider two versions with differing SHA256 to be the same

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Jammy:
  Fix Committed
Status in apt source package in Lunar:
  Fix Committed
Status in apt source package in Mantic:
  Fix Committed

Bug description:
  [Impact]
  APT sometimes deduplicates two debs into the same version object even if they have different SHA256 field values, causing download to fail later if one the sources also defines SHA512 (or MD5 or SHA1).

  This is a problem for example, if you rebuild in a PPA because PPAs do
  not have SHA512 enabled but the priamary archive does.

  Repositories are not required to have SHA256, so this does nothing if
  we do not have SHA256 for both .deb.

  [Test plan]
  An automated test is included in apt's extensive autopkgtest regression test suite. Successful pass of autopkgtest is the goal.

  [Where problems could occur]
  In terms of regressions it seems unlikely, because we compare the SHA256 only if we previously would have considered them the same version to reject them if they differ.

  But of course there could be the usual unsafe memory bugs.

  In a future this will bite us when we migrated to SHA3 and want to
  drop SHA256, just like we cannot seem to drop MD5 now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2029268/+subscriptions