Activity log for bug #1274466

Date Who What changed Old value New value Message
2014-01-30 11:25:33 Steve Langasek bug added bug
2014-01-30 11:25:58 Steve Langasek bug added subscriber Colin Watson
2014-01-30 11:26:03 Steve Langasek bug added subscriber Adam Conrad
2014-01-30 11:26:15 Steve Langasek bug added subscriber William Grant
2014-01-30 14:12:56 Michael Vogt apt (Ubuntu): importance Undecided Critical
2014-03-13 11:22:40 Anders apt (Ubuntu): status New Confirmed
2014-05-26 12:04:48 Steve Langasek apt (Ubuntu): assignee Michael Vogt (mvo)
2014-06-04 09:37:24 Michael Vogt attachment added possible fix https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1274466/+attachment/4125218/+files/apt-lp1274466.patch
2014-06-04 10:05:10 Michael Vogt attachment added Add compatbility with the prev db layout https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1274466/+attachment/4125263/+files/apt-cachedb-compat-lp1274466.diff
2014-06-04 10:05:23 Michael Vogt apt (Ubuntu): status Confirmed In Progress
2014-06-04 12:20:37 Ubuntu Foundations Team Bug Bot tags patch
2014-06-10 22:20:17 Launchpad Janitor branch linked lp:debian/apt
2014-06-12 09:08:21 Michael Vogt nominated for series Ubuntu Trusty
2014-06-12 09:08:21 Michael Vogt bug task added apt (Ubuntu Trusty)
2014-06-12 09:08:31 Michael Vogt apt (Ubuntu Trusty): status New In Progress
2014-06-12 09:08:35 Michael Vogt apt (Ubuntu): status In Progress Fix Released
2014-06-12 09:12:39 Michael Vogt apt (Ubuntu Trusty): importance Undecided High
2014-06-25 15:22:32 Michael Vogt nominated for series Ubuntu Precise
2014-06-25 15:22:32 Michael Vogt bug task added apt (Ubuntu Precise)
2014-06-25 15:25:40 Michael Vogt description 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 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.
2014-06-25 15:25:57 Michael Vogt apt (Ubuntu Precise): status New In Progress
2014-07-09 06:17:57 Chris Halse Rogers apt (Ubuntu Precise): status In Progress Fix Committed
2014-07-09 06:18:02 Chris Halse Rogers bug added subscriber Ubuntu Stable Release Updates Team
2014-07-09 06:18:04 Chris Halse Rogers bug added subscriber SRU Verification
2014-07-09 06:18:16 Chris Halse Rogers tags patch patch verification-needed
2014-07-09 06:51:10 Launchpad Janitor branch linked lp:ubuntu/precise-proposed/apt
2014-07-15 17:07:00 Colin Watson apt (Ubuntu Trusty): status In Progress Fix Committed
2014-07-15 17:22:22 Launchpad Janitor branch linked lp:ubuntu/trusty-proposed/apt
2014-09-09 05:21:38 Michael Vogt 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. 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.
2014-09-09 06:56:42 Michael Vogt 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. 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.
2014-09-17 03:06:51 Mathew Hodson apt (Ubuntu Trusty): status Fix Committed In Progress
2014-09-17 03:08:47 Mathew Hodson apt (Ubuntu Precise): status Fix Committed In Progress
2014-09-20 21:52:12 Mathew Hodson tags patch verification-needed patch verification-failed
2014-12-08 16:19:57 Mathew Hodson bug added subscriber Ubuntu Sponsors Team
2014-12-10 20:20:07 Mathew Hodson tags patch verification-failed patch
2014-12-10 20:20:36 Mathew Hodson tags patch patch precise
2015-01-07 09:47:34 Sebastien Bacher removed subscriber Ubuntu Sponsors Team
2015-08-17 00:27:31 Mathew Hodson tags patch precise patch precise trusty
2015-08-17 00:27:41 Mathew Hodson apt (Ubuntu Precise): status In Progress Confirmed
2015-08-17 00:27:45 Mathew Hodson apt (Ubuntu Trusty): status In Progress Confirmed
2015-08-17 00:33:11 Mathew Hodson 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. [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
2015-08-17 00:33:40 Mathew Hodson bug added subscriber Ubuntu Review Team
2015-09-18 05:47:20 Mathew Hodson apt (Ubuntu Precise): importance Undecided High
2015-09-18 05:47:25 Mathew Hodson apt (Ubuntu Precise): status Confirmed Triaged
2015-09-18 05:47:27 Mathew Hodson apt (Ubuntu Trusty): status Confirmed Triaged
2015-09-18 05:48:00 Mathew Hodson apt (Ubuntu Precise): milestone precise-updates
2015-09-18 05:48:03 Mathew Hodson apt (Ubuntu Trusty): milestone trusty-updates
2021-10-14 01:12:48 Steve Langasek apt (Ubuntu Precise): status Triaged Won't Fix