Activity log for bug #772052

Date Who What changed Old value New value Message
2011-04-27 22:03:05 Brian Murray bug added bug
2011-04-27 22:05:27 Brian Murray attachment added no-zero-byte-files.patch https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/772052/+attachment/2092186/+files/no-zero-byte-files.patch
2011-04-27 22:25:45 Brian Murray nominated for series Ubuntu Natty
2011-04-27 22:25:45 Brian Murray bug task added update-manager (Ubuntu Natty)
2011-04-27 22:38:13 Launchpad Janitor branch linked lp:~brian-murray/update-manager/no-zero-byte-files
2011-04-28 15:01:20 Launchpad Janitor branch linked lp:update-manager
2011-04-28 16:15:35 Brian Murray update-manager (Ubuntu Natty): status New Triaged
2011-04-28 16:15:38 Brian Murray update-manager (Ubuntu Natty): milestone natty-updates
2011-04-28 16:15:49 Brian Murray update-manager (Ubuntu Natty): importance Undecided Low
2011-04-28 16:30:40 Michael Vogt update-manager (Ubuntu Natty): status Triaged In Progress
2011-04-28 16:30:44 Michael Vogt update-manager (Ubuntu): status New In Progress
2011-04-28 16:31:10 Michael Vogt bug added subscriber Ubuntu Stable Release Updates Team
2011-05-02 12:32:21 Michael Vogt update-manager (Ubuntu): status In Progress Fix Released
2011-05-02 12:32:23 Michael Vogt update-manager (Ubuntu): importance Undecided Medium
2011-05-02 12:35:07 Michael Vogt description Binary package hint: update-manager I've seen multiple bug reports with an attachment named VarLogDistUpgradeTermlog.gz that is 37 bytes and contains no data. (See bug 701317 for an example) I believe update-manager creates this log file (term.log) before actually writing to it so we have a 0 byte file. Then if update-manager crashes (when doing a distribution upgrade) all the files in /var/log/dist-upgrade are passed to apport and added to bug reports as attachments. Then when trying to work with these attachments in Launchpad we receive an unexpected end of file. Binary package hint: update-manager TEST CASE: - regression test should be enough as its not clear what the best way to trigger this problem is the fix is pretty trivial I've seen multiple bug reports with an attachment named VarLogDistUpgradeTermlog.gz that is 37 bytes and contains no data. (See bug 701317 for an example) I believe update-manager creates this log file (term.log) before actually writing to it so we have a 0 byte file. Then if update-manager crashes (when doing a distribution upgrade) all the files in /var/log/dist-upgrade are passed to apport and added to bug reports as attachments. Then when trying to work with these attachments in Launchpad we receive an unexpected end of file.
2011-05-03 06:22:44 Martin Pitt update-manager (Ubuntu Natty): status In Progress Fix Committed
2011-05-03 06:22:47 Martin Pitt bug added subscriber SRU Verification
2011-05-03 06:22:51 Martin Pitt tags verification-needed
2011-05-03 22:26:24 Jean-Baptiste Lallement tags verification-needed verification-done
2011-05-10 06:14:05 Launchpad Janitor update-manager (Ubuntu Natty): status Fix Committed Fix Released
2011-09-19 20:54:03 Ubuntu Foundations Team Bug Bot tags verification-done testcase verification-done