Bug#852318: lightning: Fake mtime in packaged files

2017-01-29 Thread Peter Lebbing
On 28/01/17 20:42, Carsten Schoenert wrote: > then I don't understand your first email. Do I need to clarify more or did my follow-up mail already do that? > So I have currently no clue where the timestamps with *.0 are > coming from. Maybe I'm nitpicking, maybe I'm pointing out somethin

Bug#852318: lightning: Fake mtime in packaged files

2017-01-28 Thread Carsten Schoenert
Hi Peter, On Sat, Jan 28, 2017 at 05:45:30PM +0100, Peter Lebbing wrote: > 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 > > chang

Bug#852318: lightning: Fake mtime in packaged files

2017-01-28 Thread Peter Lebbing
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-visib

Bug#852318: lightning: Fake mtime in packaged files

2017-01-28 Thread Carsten Schoenert
Helo Peter, On Mon, Jan 23, 2017 at 03:52:14PM +0100, Peter Lebbing wrote: ... > I suggest these synthetic, fake mtimes should be fixed to reflect actual > changes. I can't believe that someone wrote the two versions of > menuOverlay.dtd with two different access keys in the same, very first > se

Bug#852318: lightning: Fake mtime in packaged files

2017-01-23 Thread Peter Lebbing
Package: lightning Version: 1:45.6.0-3 Severity: normal Dear maintainer, Some packaged files have fake, constant modification times, as can for instance be seen here: ll --full-time usr/lib/lightning/ total 40 -rw-r--r-- 1 peter peter 563 2010-01-01 01:00:00.0 +0100 app.ini drwxr-xr-x 2