Hello Carsten, On 28/01/17 17:15, Carsten Schoenert wrote: > we didn't ever have done some patching here. I did a quick search on the > upstream sources and found mozilla bug 1277976 which introduces this > change.
While this sure is the change that made the mtime problem manifest with user-visible changes, this change is not the problem. > I suggest to get in contact with upstream by simply answering in the bug > report with your analyze. We can patch the source once the position of > usptream is clear. I wonder if this is appropriate. IMO, the bug is about something else entirely. It's just that the fix effected a different problem. Mozilla bug #1277976 is about what users expect a certain keyboard shortcut does, in a nutshell. This Debian bug report I opened is about (many) files having fake metadata, confusing backup tools. While the one led to the other in this specific instance, they are in essence unrelated. If you really suggest I bring it up in that bug report, I'll do so. But it feels like conflating issues in a single bug report. I could also open a new upstream bug report. I'm always a bit uncertain whether to report upstream or to Debian. I'm using Debian, it feels like I should report it there. But I'm also using upstream, right... I think in any case Debian should be aware of this specific issue, and decide whether to fix this in stable as well. For users of a whole class of backup solutions, it's a potential, but relatively benign data-loss issue. Only filesystem-specific tools and backup tools that always compare or checksum every byte of every file in the filesystem will not be fooled by the fake metadata. Thanks, Peter. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at <http://digitalbrains.com/2012/openpgp-key-peter>
