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

Bug#357162: marked as done (debian-policy: preserve /usr/share/doc/*/* timestamps)

Your message dated Wed, 26 Apr 2006 11:25:27 -0500
with message-id <87vesw9udk.fsf@glaurung.internal.golden-gryphon.com>
and subject line Bug#357162: debian-policy: preserve /usr/share/doc/*/* timestamps
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: debian-policy
Severity: wishlist

Many /usr/share/doc/*/* file maintainers don't
cp --preserve=timestamps (cp -p) their updates. Thus upon ls -l,
README.blorg looks like it was updated yesterday, when in fact it
hasn't changed since 2002, upstream or downstream.

I recall somewhere in some documents a recommendation on keeping
original dates, but even many of the sharpest Debian developers aren't
hip to cp -p, or cp -a yet. There must be hundreds of packages like
this. I suppose I shall find that policy paragraph and file a wishlist
bug against such a package when I encounter it.

Here offline my slightly stale
12.3 Additional documentation
doesn't mention it. Here policy should urge it.

says to follow the above policy, so putting it into policy would be
seen by readers of the Developer's Reference too.

--- End Message ---
--- Begin Message ---

        Policy already has a suggestion to preserve timestamps.

Ducks?  What ducks??
Manoj Srivastava   <srivasta@debian.org>  <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

--- End Message ---

Reply to: