Hi Chris,
A modified version of the suggested patch has been committed to SVN but
hasn't been uploaded yet.
Before uploading the package I'd like to understand who is going to set
the DEB_BUILD_DATE variable. It could be set by maven-debian-helper but
this would be Java specific. I think it
FTR I'm working on a slightly modified patch and I expect to upload it soon.
Emmanuel Bourg
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Sat, Jan 10, 2015 at 10:19:19PM +0100, Emmanuel Bourg wrote:
Thank you for the update. It's safe to assume the date always follow the
comment specified, the Javadoc for the store() method states:
Next, a comment line is always written, consisting of an ASCII #
character, the current date
Yeah, DEB_BUILD_DATE makes me less uneasy, too.
I've updated the patch to replace the line. This assumes
that it is present; would be great if this kind of thing
was specified. It's hard to verify the assumption as the
date comes out in locale format.
From
Le 10/01/2015 17:54, Chris West a écrit :
I've updated the patch to replace the line. This assumes
that it is present; would be great if this kind of thing
was specified. It's hard to verify the assumption as the
date comes out in locale format.
Thank you for the update. It's safe to
Hi Chris,
Thank you very much for the patch. I think it could be simplified by
writing the properties in memory, replacing the line containing the date
if the BUILD_DATE variable is detected, and then saving the file. This
would avoid duplicating the code serializing the properties.
Is the
Package: libmaven-archiver-java
Version: 2.5-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain
Hi!
While working on the “reproducible builds” effort [1], we have noticed
that many Java packages would not build reproducibly because Maven emits
7 matches
Mail list logo
