modifies .uploaded time every time whoopsie starts

This may only be happening for .uploaded files with a corresponding .upload and / or .crash file.

Yeah, in src/whoopsie.c:process_existing_files we definitely check to see if we've handled the report already, then mark it as seen. I'm not entirely sure why I did this, but I vaguely recall thinking about corner cases in already_handled_report. We should fix this, but we should be very careful to ensure we've covered all the bases.

As discussed offline, the original reason for marking reports as seen after we've confirmed that they have already been seen is to handle cases like the .crash file not existing when a .upload does. Not marking these as seen though does not seem to save us any time though, and we could clean these up in the cron.daily job.

The solution here will be to drop the mark_seen code after already_handled_report.

This bug was fixed in the package whoopsie - 0.2.9

---------------
whoopsie (0.2.9) raring; urgency=low

  * Do not modify the .uploaded file corresponding to a .crash file when
    starting up (LP: #1084311)
 -- Brian Murray <email address hidden> Tue, 11 Dec 2012 10:16:56 -0800

This is important to SRU because you could run into a situation like this:

You experience a crash for a second time (update-notifier doesn't tell you about it for some reason) and then you have a .crash file newer than a .uploaded file. Some time later you reboot and when whoopsie restarts the .uploaded file becomes newer than the .crash file. When reviewing you reports directory whoopsie determines that it has already sent your .crash file since the .uploaded file is newer than it and your second instance of the crash is not sent to errors.

I've uploaded this to the quantal -proposed queue.

Hello Brian, or anyone else affected,

Accepted whoopsie into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/whoopsie/0.2.7.1 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!

verified, using the steps in the description, that (1) current whoppsie did not upload an updated crashdump, and (2) whoppsie from -proposed *did* upload a newer crash.

Tagging verification-done.

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

This bug was fixed in the package whoopsie - 0.2.7.1

---------------
whoopsie (0.2.7.1) quantal-proposed; urgency=low

  * Do not modify the .uploaded file corresponding to a .crash file when
    starting up (LP: #1084311)
 -- Brian Murray <email address hidden> Thu, 13 Dec 2012 16:26:40 -0800