On Thu 2015-06-04 21:51:37 -0400, Brendan O'Dea wrote:
Local times, and daylight savings are just too much of a PITA. Just
use UTC and if builds on the first of the month are possibly different
to the changelog, so be it.
I agree with Brendan here.
If there are no objections to the idea that
Jérémy Bobbio wrote:
We use BUILD_DATE=$(dpkg-parsechangelog -S Date) to get the time of
the latest debian/changelog entry. Other projects could use
BUILD_DATE=$(git log -1 --pretty=%cd).
Hah! I use git log -1 --format='tformat:%ct' for this situation in the tzcode
distribution. Great minds
On Thu 2015-06-04 09:53:11 -0400, Thomas Schmitt wrote:
I saw some sin-list page about packages shortly after
xorriso-1.4.0 was released.
It complained about libburn's doc/doxygen.conf.in which i hope to
have fixed by
http://libburnia-project.org/changeset/5446
Thanks! We don't think it's
On Thu 2015-06-04 10:38:53 -0400, Ximin Luo wrote:
A few months ago I had an idea for this that would be more generalisable. See
https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20150330/001317.html
for details. TL;DR is to have SOURCEDATE as an environment variable
On 04/06/15 19:30, Daniel Kahn Gillmor wrote:
What TZ should SOURCEDATE have? ISO8601 is capable of supplying a TZ as
well, so the current time could be written in a wide variety of ways
while meaning the same instant:
0 dkg@alice:~$ date '+%FT%T%z' date -u '+%FT%T%z'
Hi,
If we can identify the specific commands (beyond what you point out
below), would there a general interest upstream in something like a
--reproducible=TARGETDATE
The syntax would have to be different and probably a more
comprehensive name will come to us when we know what xorriso
features
On Thu 2015-06-04 08:17:59 -0400, Brendan O'Dea wrote:
The idea was that unless that environment variable was set, the
behaviour would be unchanged: the current date would be used. It
seems unlikely that DEB_BUILD_CHANGELOG would be set accidentally.
right, but this wouldn't be terribly
Hi,
On Donnerstag, 4. Juni 2015, Ximin Luo wrote:
https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-2
0150330/001317.html
for details. TL;DR is to have SOURCEDATE as an environment variable in
ISO8601 format.
It would be awesome for help2man to support this. At
Hi,
on yesterday's IRC meeting we decided to do another poll for the
next and for all following IRC meetings.
So please give your vote for the timeslots where you could participate:
https://dudle.inf.tu-dresden.de/r4sm1ze4/
The times are meant to be UTC, so take adjustments for your timezone
On Thu 2015-06-04 14:08:36 -0400, Thomas Schmitt wrote:
The syntax would have to be different and probably a more
comprehensive name will come to us when we know what xorriso
features in particular shall be bundled with the new command.
That seems like a reasonable approach.
The users will
Hi,
the current situation with data extents looks not good for
the purpose of reproducability.
The files are grafted into a red-black tree according to
their inode and device numbers on hard disk. This is done
to merge hardlinks.
The tree is then serialized into an array which gets
sorted
Hi Daniel,
On Donnerstag, 4. Juni 2015, Daniel Kahn Gillmor wrote:
This patch makes it easier to point people at the list of variations
and the list of usertagged bugs. It also uses css to make the
targeted sections have a different header color (i'm happy for more
style-y people to improve
On 4 June 2015 at 00:19, Daniel Kahn Gillmor d...@fifthhorseman.net wrote:
On Wed 2015-06-03 08:24:51 -0400, Brendan O'Dea wrote:
My inclination is instead to do something fairly specific to your
project: If the environment variable DEB_BUILD_CHANGELOG (or something
similar) is set, then the
On 06/04/2015 12:31 PM, Reiner Herrmann wrote:
The poll will run for one week, then the result will be announced.
As the result of the poll might be Monday 15th and we want to announce
the result about one week in advance, the poll will be closed already
on the upcoming Monday (8th).
Regards,
The new `--clamp-mtime` option will change the behavior of `--mtime` to
only use the time specified if the file mtime is newer than the given time.
The `--clamp-mtime` option can only be used together with `--mtime`.
Typical use case is to make builds reproducible: to loose less
information, it's
Paul Eggert:
On 06/04/2015 08:59 AM, Jérémy Bobbio wrote:
BUILD_DATE=Mon, 01 Jun 2015 18:11:50 +0200
Yes, that's the hassle I was referring to. Something has to keep track of
BUILD_DATE and update it when appropriate. It would be better if this were
automated somehow. (Sorry, I don't
Source: cassiopee
Version: 1.0.3+dfsg
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: timestamps
Hi,
While working on the “reproducible builds” effort [1], we have noticed
that cassiopee could not be built reproducibly.
The attached patch changes the
Hi libburnia/xorriso folks--
I participate in the Debian Reproducible Builds project [0] (cc'ed
here). Our goal is to ensure that free software can be built from
source in a way that the binary outcome is byte-for-byte identical, so
that compromised build infrastructure can be detected.
One of
On Thu 2015-06-04 05:07:51 -0400, Holger Levsen wrote:
Cool! Thanks, merged + deployed your patch!
great, thank you, Holger!
Will you be providing links to these anchors too? ;-)
Yes, but they'll probably be external, like
https://www.debian-administration.org/users/dkg/weblog/115
If folks
On Donnerstag, 4. Juni 2015, Daniel Kahn Gillmor wrote:
If folks want to cross-link internally too, that would be great, but i
was just scratching my particular itch here :)
fair enough!
:)
signature.asc
Description: This is a digitally signed message part.
20 matches
Mail list logo
