Comment 13 for bug 175191

I had some thoughts on this earlier today, as I was manually correcting the timestamp on about 2,000 photos that F-Spot chose to corrupt for me. I'm commenting here because I believe that something should be done about this in Ubuntu until upstream comes up with a solution. I'm not holding my breath, because I distinctly remember running into this problem back in about 2006. Looking at the upstream bug, it looks like this has been open for at least that long.

Upstream doesn't seem to have a clear idea of what to do about this, and they seem to have rejected the obvious (to me) solution of not touching the timestamp. I'd love to see a checkbox; "Modify timestamps during import?"

Barring that, however, there are patches available to F-Spot to cause it not to modify timestamps. Is it possible for Ubuntu to distribute F-Spot with one of these patches applied?

At the very least, I'm going to study up on deb packaging and see if I can't roll my own patched F-Spot package.

I don't mean to stir up any trouble here, but some noise needs to be made about this, and something needs to get done.