[Bug 2029268] Re: Do not consider two versions with differing SHA256 to be the same

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 2.7.3

---------------
apt (2.7.3) unstable; urgency=medium

  [ Tianon Gravi ]
  * Add "apt-patterns" reference to "apt list" description in apt(8)

  [ Frans Spiesschaert ]
  * Dutch manpages translation update (Closes: #1033904)
  * Dutch program translation update (Closes: #1033909)

  [ Mert Dirik ]
  * Turkish program translation update

  [ Remus-Gabriel Chelu ]
  * Romanian program translation update (Closes: #1040644)

  [ David Kalnischkies ]
  * Add apt-patterns(7) to apt{,-cache,-get} SEE ALSO sections

  [ Julian Andres Klode ]
  * Compare SHA256 to check if versions are really the same (Closes: #931175)
    (LP: #2029268)

 -- Julian Andres Klode <jak at debian.org>  Wed, 02 Aug 2023 14:30:47
+0200

** Changed in: apt (Ubuntu Mantic)
       Status: Fix Committed => Fix Released

-- 
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 Released
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 Released

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