On Wed, 26 Apr 2006 10:39:51 -0600
"Shaun Jackman" <[EMAIL PROTECTED]> wrote:
> Hold off on the debhelper bug for now, perhaps. The dpkg-source
> utility from the dpkg-dev package seems like a better place to start...
> > > That dpkg-source doesn't preserve
> > > time stamps is a straight-forward bug.
> >
> > Has it been reported already?
>
> Not yet.
If you're too busy to report it I'd do it, but probably not half
as well, since I haven't yet used 'dpkg-source' and don't quite know
what to look for. The symptoms seem plain enough though.
Looking at the bug list for 'dpkg-dev', I notice several 'dpkg-source'
bugs that mention timestamps, for instance:
[DPKG-SOURCE] touch all patched files to avoid race conditions
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=105750
[DPKG-SOURCE] applying patch causes timestamps to skew and upset make
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=208276
...a quote from the latter bug:
9/1/03 Dirk Eddelbuettel replies to Daniel Schepler:
> I've heard this is going to be fixed in dpkg-source v2, by saving time
> stamps in the diff.gz.
Yes, agreed. This patching/timestamp issue is old.
Why there's no official bug for it (or if so, where) is beyond me.
> > ...Either way though, I'd agree that it would be useful for our
> > purposes to have time stamps in patches, unless there are
> > compelling though seldom heard reasons not to.
>
> I would be interested to hear any argument against including the time
> stamp information in the .diff.gz.
<sounds of crickets chirping>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
