[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#417637: marked as done (apt: policy: timestamps)

Your message dated Mon, 22 Dec 2008 19:10:15 +0800
with message-id <87ocz4bh48.fsf@jidanni.org>
and subject line Re: Bug#417637: state of #417637
has caused the Debian Bug report #417637,
regarding apt: policy: timestamps
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
417637: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417637
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 0.6.46.4
Severity: minor

$ dlocate -L apt|xargs ls -tdog|sed /^d/d
Shows apt apparently doesn't follow policy:

4.7. Time Stamps
----------------

     Maintainers should preserve the modification times of the upstream
     source files in a package, as far as is reasonably possible.[1]

[1]  The rationale is that there is some information conveyed by knowing
     the age of the file, for example, you could recognize that some
     documentation is very old by looking at the modification time, so it
     would be nice if the modification time of the upstream source would be
     preserved.

At least if a file has not changed, then its timestamp should not look
new, upstream or not.

--- End Message ---
--- Begin Message --- 
EVL> I don't understand the problem.
EVL> I see files with their timestamps. And?

Well, "they couldn't have been all last edited at the same moment"...
but I suppose these days everything is the result of postprocessing... closing.

--- End Message ---
Reply to: