Jérémy Bobbio:
Jonathan Nieder:
I disagree that this is important information. Most packages that I have
seen so far do not propagate timestamps when copying a file from source.
Could you give me an example of one that would do so?
See
Hi,
Jérémy Bobbio wrote:
Guillem Jover:
For example, in the generated data.tar the files will contain
different modification times, some will come untouched from the source
files if they just get copied, and others will be newer if the files
got created at build time. Preserving these
Jonathan Nieder:
I disagree that this is important information. Most packages that I have
seen so far do not propagate timestamps when copying a file from source.
Could you give me an example of one that would do so?
See http://www.debian.org/doc/debian-policy/ch-source.html#s-timestamps
Jérémy Bobbio:
Guillem Jover:
The timestamp on the ar member let's you know when the package got
built.
I don't believe this add much value: we have this information in the
.changes files already.
Anyway, I was thinking of adding a `--timestamp=1377619307` option to
`dpkg-deb`. The
Hi!
Guillem Jover:
I've been thinking about this, and I think you might be trying to
solve the problem in the wrong place(s), and possibly there's a need
to step back and ponder about what do you really want out of all this,
to know where or how to best fix it.
[…]
My ideal scenario is the
Hi!
On Fri, 2013-08-16 at 08:45:47 -0400, Asheesh Laroia wrote:
On Fri, 16 Aug 2013, Guillem Jover wrote:
The same will apply when building that deb package multiple times,
the timestamps will change for the ar headers. And I don't really
want to lose that data, because currently is the only
Hi!
On Thu, 2013-08-15 at 19:42:17 -0400, Asheesh Laroia wrote:
Package: dpkg
Version: 1.16.10
Severity: normal
Summary: In lib/dpkg/compress.c, I would like it if dpkg did not
store timestamps in the gzip files. That way, the creation of the
data.tar.gz would be deterministic.
In
Hi!
On Fri, 2013-08-16 at 08:58:02 +0200, Guillem Jover wrote:
On Thu, 2013-08-15 at 19:42:17 -0400, Asheesh Laroia wrote:
Package: dpkg
Version: 1.16.10
Severity: normal
Summary: In lib/dpkg/compress.c, I would like it if dpkg did not
store timestamps in the gzip files. That way,
On Fri, 16 Aug 2013, Guillem Jover wrote:
The same will apply when building that deb package multiple times, the
timestamps will change for the ar headers. And I don't really want to
lose that data, because currently is the only place were the build time
information is recorded. Do you only
On Fri, 16 Aug 2013, Guillem Jover wrote:
dpkg has not used the gzip command for a very long long time (prior to
dpkg 1.9.x), and zlib does not initialize the gzip header, so the
timestamp should be 0. If there are differences these should come from
something else, like different tar files fo
Package: dpkg
Version: 1.16.10
Severity: normal
*** Please type your report below this line ***
Summary: In lib/dpkg/compress.c, I would like it if dpkg did not store
timestamps in the gzip files. That way, the creation of the data.tar.gz
would be deterministic.
In particular, when I build
11 matches
Mail list logo
