[Touch-packages] [Bug 1274466] Re: apt-ftparchive on-disk cache format changed between lucid and precise, results in Packages files with silently corrupted checksums fields
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: apt (Ubuntu Precise) Status: Triaged => Won't Fix -- 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/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: Won't Fix Status in apt source package in Trusty: Triaged Bug description: [Impact] 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. [Test Case] * generate a cachedb with apt-ftparchive from lucid via apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb > Packages.1 * use apt-ftparchive from precise and run apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb > Packages.2 and verify that it generates different hashes than Packages.1 (diff -u Packages.1 Packages.2) * use apt-ftparchive from precise-proposed and run: apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb > Packages.3 and verify that the hashes are identical to the ones in Packages.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1274466/+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
[Touch-packages] [Bug 1274466] Re: apt-ftparchive on-disk cache format changed between lucid and precise, results in Packages files with silently corrupted checksums fields
** Changed in: apt (Ubuntu Precise) Importance: Undecided => High ** Changed in: apt (Ubuntu Precise) Status: Confirmed => Triaged ** Changed in: apt (Ubuntu Trusty) Status: Confirmed => Triaged ** Changed in: apt (Ubuntu Precise) Milestone: None => precise-updates ** Changed in: apt (Ubuntu Trusty) Milestone: None => trusty-updates -- 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/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: Triaged Status in apt source package in Trusty: Triaged Bug description: [Impact] 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. [Test Case] * generate a cachedb with apt-ftparchive from lucid via apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb > Packages.1 * use apt-ftparchive from precise and run apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb > Packages.2 and verify that it generates different hashes than Packages.1 (diff -u Packages.1 Packages.2) * use apt-ftparchive from precise-proposed and run: apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb > Packages.3 and verify that the hashes are identical to the ones in Packages.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1274466/+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
[Touch-packages] [Bug 1274466] Re: apt-ftparchive on-disk cache format changed between lucid and precise, results in Packages files with silently corrupted checksums fields
** Tags added: trusty ** Changed in: apt (Ubuntu Precise) Status: In Progress = Confirmed ** Changed in: apt (Ubuntu Trusty) Status: In Progress = Confirmed -- 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/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: Confirmed Status in apt source package in Trusty: Confirmed Bug description: [Impact] 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. [Test Case] * generate a cachedb with apt-ftparchive from lucid via apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.1 * use apt-ftparchive from precise and run apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.2 and verify that it generates different hashes than Packages.1 (diff -u Packages.1 Packages.2) * use apt-ftparchive from precise-proposed and run: apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.3 and verify that the hashes are identical to the ones in Packages.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1274466/+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
[Touch-packages] [Bug 1274466] Re: apt-ftparchive on-disk cache format changed between lucid and precise, results in Packages files with silently corrupted checksums fields
** Description changed: - TEST CASE: - 1. generate a cachedb with apt-ftparchive from lucid via - apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.1 - - use apt-ftparchive from precise and run - apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.2 - and verify that it generates different hashes than Packages.1 (diff -u Packages.1 Packages.2) - - use apt-ftparchive from precise-proposed and run: - apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.3 - and verify that the hashes are identical to the ones in Packages.1 + [Impact] 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 + 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. + + [Test Case] + + * generate a cachedb with apt-ftparchive from lucid via + apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.1 + + * use apt-ftparchive from precise and run + apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.2 + and verify that it generates different hashes than Packages.1 + (diff -u Packages.1 Packages.2) + + * use apt-ftparchive from precise-proposed and run: + apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.3 + and verify that the hashes are identical to the ones in Packages.1 -- 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/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: Confirmed Status in apt source package in Trusty: Confirmed Bug description: [Impact] 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. [Test Case] * generate a cachedb with apt-ftparchive from lucid via apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.1 * use apt-ftparchive from precise and run apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.2 and verify that it generates different hashes than Packages.1 (diff -u Packages.1 Packages.2) * use apt-ftparchive from precise-proposed and run: apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.3 and verify that the hashes are identical to the ones in Packages.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1274466/+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
[Touch-packages] [Bug 1274466] Re: apt-ftparchive on-disk cache format changed between lucid and precise, results in Packages files with silently corrupted checksums fields
** Tags removed: verification-failed ** Tags added: precise -- 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/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: 1. generate a cachedb with apt-ftparchive from lucid via apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.1 - use apt-ftparchive from precise and run apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.2 and verify that it generates different hashes than Packages.1 (diff -u Packages.1 Packages.2) - use apt-ftparchive from precise-proposed and run: apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.3 and verify that the hashes are identical to the ones in Packages.1 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 -- 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
[Touch-packages] [Bug 1274466] Re: apt-ftparchive on-disk cache format changed between lucid and precise, results in Packages files with silently corrupted checksums fields
** Tags removed: verification-needed ** Tags added: verification-failed -- 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/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: 1. generate a cachedb with apt-ftparchive from lucid via apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.1 - use apt-ftparchive from precise and run apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.2 and verify that it generates different hashes than Packages.1 (diff -u Packages.1 Packages.2) - use apt-ftparchive from precise-proposed and run: apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.3 and verify that the hashes are identical to the ones in Packages.1 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 -- 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
[Touch-packages] [Bug 1274466] Re: apt-ftparchive on-disk cache format changed between lucid and precise, results in Packages files with silently corrupted checksums fields
This SRU has been shadowed by a security update and needs to be re- merged. ** Changed in: apt (Ubuntu Trusty) Status: Fix Committed = In Progress ** Changed in: apt (Ubuntu Precise) Status: Fix Committed = In Progress -- 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/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: 1. generate a cachedb with apt-ftparchive from lucid via apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.1 - use apt-ftparchive from precise and run apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.2 and verify that it generates different hashes than Packages.1 (diff -u Packages.1 Packages.2) - use apt-ftparchive from precise-proposed and run: apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.3 and verify that the hashes are identical to the ones in Packages.1 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 -- 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
[Touch-packages] [Bug 1274466] Re: apt-ftparchive on-disk cache format changed between lucid and precise, results in Packages files with silently corrupted checksums fields
** Description changed: TEST CASE: 1. generate a cachedb with apt-ftparchive from lucid via apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.1 - 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 + apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.2 + and verify that it generates different hashes than Packages.1 (diff -u Packages.1 Packages.2) - 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 + apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.3 + and verify that the hashes are identical to the ones in Packages.1 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. -- 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/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: Fix Committed Status in “apt” source package in Trusty: Fix Committed Bug description: TEST CASE: 1. generate a cachedb with apt-ftparchive from lucid via apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.1 - use apt-ftparchive from precise and run apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.2 and verify that it generates different hashes than Packages.1 (diff -u Packages.1 Packages.2) - use apt-ftparchive from precise-proposed and run: apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.3 and verify that the hashes are identical to the ones in Packages.1 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 -- 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
[Touch-packages] [Bug 1274466] Re: apt-ftparchive on-disk cache format changed between lucid and precise, results in Packages files with silently corrupted checksums fields
** Description changed: - Test case: - - generate a cachedb with apt-ftparchive from lucid via -apt-ftparchive --db old-db 2vcard_0.5-3_all.deb + TEST CASE: + 1. generate a cachedb with apt-ftparchive from lucid via + apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.1 - 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 + 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 + 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. + 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. -- 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/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: Fix Committed Status in “apt” source package in Trusty: Fix Committed Bug description: TEST CASE: 1. generate a cachedb with apt-ftparchive from lucid via apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.1 - 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 -- 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
[Touch-packages] [Bug 1274466] Re: apt-ftparchive on-disk cache format changed between lucid and precise, results in Packages files with silently corrupted checksums fields
Hello Steve, or anyone else affected, Accepted apt into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.2 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: apt (Ubuntu Trusty) Status: In Progress = Fix Committed -- 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/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: Fix Committed Status in “apt” source package in Trusty: Fix Committed 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 -- 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
