[Bug 1274466] Re: apt-ftparchive on-disk cache format changed between lucid and precise, results in Packages files with silently corrupted checksums fields

[Michael Vogt]

** Also affects: apt (Ubuntu Precise)
   Importance: Undecided
       Status: New

** Description changed:

- The archive.ubuntu.com master server has just been upgraded from lucid
- to precise.  As a result, the apt version went from 0.7.25.3 to
- 0.8.16~exp12, and apparently some time in that interval the on-disk
- format of apt-ftparchive's cache changed.
+ Test case:
+ - generate a cachedb with apt-ftparchive from lucid via
+    apt-ftparchive --db old-db 2vcard_0.5-3_all.deb
+ - use apt-ftparchive from precise and run
+    apt-ftparchive --db old-db 2vcard_0.5-3_all.deb
+   and verify that the hashsums are no longer correct
+ - use apt-ftparchive from precise-proposed and run:
+     apt-ftparchive --db old-db 2vcard_0.5-3_all.deb
+   and verify that the hashes are correct now
+ 
+ 
+ The archive.ubuntu.com master server has just been upgraded from lucid to precise.  As a result, the apt version went from 0.7.25.3 to 0.8.16~exp12, and apparently some time in that interval the on-disk format of apt-ftparchive's cache changed.
  
  This wouldn't be a problem, except apt-ftparchive itself doesn't
  *notice* that the cache format has changed, and instead happily reads
  the existing files and parses them incorrectly, resulting in corrupted
  checksums output in the Packages file for each of the .debs.
  
  apt-ftparchive should version its file formats so that it correctly
  notices incompatible cache files.

** Changed in: apt (Ubuntu Precise)
       Status: New => In Progress

-- 
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/1274466

Title:
  apt-ftparchive on-disk cache format changed between lucid and precise,
  results in Packages files with silently corrupted checksums fields

Status in “apt” package in Ubuntu:
  Fix Released
Status in “apt” source package in Precise:
  In Progress
Status in “apt” source package in Trusty:
  In Progress

Bug description:
  Test case:
  - generate a cachedb with apt-ftparchive from lucid via
     apt-ftparchive --db old-db 2vcard_0.5-3_all.deb
  - use apt-ftparchive from precise and run
     apt-ftparchive --db old-db 2vcard_0.5-3_all.deb
    and verify that the hashsums are no longer correct
  - use apt-ftparchive from precise-proposed and run:
      apt-ftparchive --db old-db 2vcard_0.5-3_all.deb
    and verify that the hashes are correct now

  
  The archive.ubuntu.com master server has just been upgraded from lucid to precise.  As a result, the apt version went from 0.7.25.3 to 0.8.16~exp12, and apparently some time in that interval the on-disk format of apt-ftparchive's cache changed.

  This wouldn't be a problem, except apt-ftparchive itself doesn't
  *notice* that the cache format has changed, and instead happily reads
  the existing files and parses them incorrectly, resulting in corrupted
  checksums output in the Packages file for each of the .debs.

  apt-ftparchive should version its file formats so that it correctly
  notices incompatible cache files.

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