Hi, On Thu, 28 Aug 2014, Niko Tyni wrote: > In the scope of just the source package, it seems possible for dpkg-source > to remember the latest timestamp it has extracted and notice if that's > newer than the debian/changelog timestamp.
dpkg-source delegates most of the extraction to "tar" so it would have to scan the directory again to find out the timestamps (or at least scan the tar archive again). > > This also gets more complicated when dealing with NFS mounts, which > > the current code is already handling correctly. > > Could you elaborate a bit on that? Is there some NFS specific code in > dpkg-source at the moment? See Dpkg::Source::Functions::fs_time() at least. > > Although some of these situations might show up from timestamp skews > > due to mismatched times from upstream, packager, or build systems for > > example, that's just a reality that I'm not sure we can ignore. > > Yeah, I see it's complicated. > > Do you think an archive-wide check for source packages having newer > files than their debian/changelog timestamps might tip the scales, or > is it clear that this is just not going to work? (I guess lintian would > be a good place for such a check.) The probability of having an older timestamp in debian/changelog seems rather low to me. I don't really understand Guillem's concerns here. However, for the few cases where it might lead to some problems, we might want to reset the timestamp of the patched files before build so that the packager detects it on build and not later when someone unpacks it for the first time. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
