Activity log for bug #1045704
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2012-09-04 09:09:27 | Sebastien Bacher | bug | added bug | ||
| 2012-09-04 09:48:57 | Michael Vogt | apt (Ubuntu): status | New | In Progress | |
| 2012-09-04 09:48:59 | Michael Vogt | apt (Ubuntu): importance | Undecided | High | |
| 2012-09-04 10:46:15 | Michael Vogt | nominated for series | Ubuntu Precise | ||
| 2012-09-04 10:46:15 | Michael Vogt | bug task added | apt (Ubuntu Precise) | ||
| 2012-09-04 10:46:23 | Michael Vogt | apt (Ubuntu): status | In Progress | Fix Released | |
| 2012-09-04 10:46:29 | Michael Vogt | apt (Ubuntu Precise): status | New | Triaged | |
| 2012-09-04 11:43:25 | Michael Vogt | description | The issue is reported from a precise system upgraded over time, it seems that pkgcache.bin.<random> and srcpkgcache.bin.<random> are left over time in /var/cache/apt/, those should be cleaned | TEST CASE: 1. do sudo touch /var/cache/apt/pkgcache.bin.xxx to simulate atmoic write that did not get cleaned up 2. run sudo apt-get update 3. verify that the file is still there 4. install apt from precise-proposed 5. run sudo apt-get update 6. verify that the file is now cleaned up The issue is reported from a precise system upgraded over time, it seems that pkgcache.bin.<random> and srcpkgcache.bin.<random> are left over time in /var/cache/apt/, those should be cleaned | |
| 2012-09-04 11:43:28 | Michael Vogt | apt (Ubuntu Precise): importance | Undecided | High | |
| 2012-09-04 11:43:33 | Michael Vogt | apt (Ubuntu Precise): status | Triaged | In Progress | |
| 2012-09-04 11:43:43 | Michael Vogt | branch linked | lp:~ubuntu-core-dev/apt/precise | ||
| 2021-10-14 04:48:58 | Steve Langasek | apt (Ubuntu Precise): status | In Progress | Won't Fix |
