Dear Sir,
Sorry for the late reply.
Please find the transfer swift copy attached.
Please Confirm receipt and let us know if the order is now ready.
Regards,
Ashan Bachi
Dear Sir,
Sorry for the late reply.
Please find the transfer swift copy attached.
Please Confirm receipt and let us know if
Daniel Kahn Gillmor writes (Re: [Reproducible-builds] Reproducible Builds —
proof of concept successful for 83% of all sources in main):
However, for packages that don't use a framework we can fix, or which
use a tool that has no plans to adopt these kinds of modes upstream,
I think that if
Package: sbuild
Version: 0.65.0-1
Severity: wishlist
Tags: patch
Thanks for maintaining sbuild!
In order to use sbuild for reproducible builds, the build dir needs to
be consistent across rebuilds, but sbuild currenty generates a
randomly named build dir.
The following proof-of-concept patch
Source: witty
Version: 3.3.3+dfsg-4.1
User: reproducible-builds@lists.alioth.debian.org
Hi!
While working on Debian's “reproducible builds” effort [1], we have
noticed that witty doesn't build reproducibly [2].
There is a difference in the header file /usr/include/Wt/WConfig.h.
Depending on the
Package: sbuild
Version: 0.65.0-1
Severity: wishlist
Tags: patch
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org
Thanks for maintaining sbuild!
When using dpkg from the reproducible builds toolchain, it generates a
.buildinfo file in the .changes file:
On 2015-02-16, Holger Levsen wrote:
On Samstag, 14. Februar 2015, Vagrant Cascadian wrote:
One patch sets the build dir to a static location based on the package
version, rather than a tempdir with a random string.
The other patch ignores .buildinfo files in the .changes when displaying
Hi,
Quoting Vagrant Cascadian (2015-02-16 21:01:18)
Also, pbuilder and sbuild would need to ensure the same exact package set
from build dependencies; there are various different dependency resolvers
which might result in differences that could cause unreproducibility...
this has been taken
Daniel Kahn Gillmor:
On Fri 2015-02-13 03:36:20 -0500, Hans-Christoph Steiner wrote:
I think it would be much simpler to just have the single package signature
that is embedded in the package file itself, like Android APKs and Java JARs.
Since the package is built reproducibly, anyone who
Debian Wiki:
New page:
Java classes (.class) that were compiled by the groovy compiler (groovyc)
contain timestamps.
See also: [[http://thread.gmane.org/gmane.comp.lang.groovy.user/39306/|Thread
on groovy-user mailing list]]
= Detection =
The diff of .class files contains the string
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
11 matches
Mail list logo