Re: Moving towards a deb-buildinfo(5) Format 1.0

2016-11-14 Thread Guillem Jover
Hi! On Sun, 2016-11-13 at 14:21:45 +0100, Johannes Schauer wrote: > Also see: > > https://wiki.debian.org/ReproducibleBuilds/BuildinfoFiles#Semantics > > I've heard many upstream developers who were initially very much against > purging the timestamp when the build was done from their build arti

Re: Buildinfo in the Debian archive, updates

2016-11-14 Thread Ximin Luo
Chris Lamb: > Ximin Luo wrote: > >> This minimal solution still depends on 3rd-party services being available to >> host the files. A much better solution is for the FTP archive to *also* store >> the signed buildinfo files, somewhere safe that can be recovered when needed. > > Totally ACK. Just

Re: Buildinfo in the Debian archive, updates

2016-11-14 Thread Chris Lamb
Ximin Luo wrote: > This minimal solution still depends on 3rd-party services being available to > host the files. A much better solution is for the FTP archive to *also* store > the signed buildinfo files, somewhere safe that can be recovered when needed. Totally ACK. Just to be clear, I was neve

Bug#844362: jasperreports: FTBFS: Could not resolve dependencies for project net.sf.jasperreports:jasperreports:jar:6.2.2: The following artifacts could not be resolved: net.sf.jopt-simple:jopt-simple

2016-11-14 Thread Chris Lamb
Source: jasperreports Version: 6.2.2-2 Severity: serious Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org Dear Maintainer, jasperreports fails to build from source in unstable/amd6

Re: accessibility of the reproducible builds page

2016-11-14 Thread Chris Lamb
HW42 wrote: > diffs are indented to reflect the nested structure of the files Indeed, this is something inherent, at least from an abstract point of view, in the output format. Despite that, we could have a separate text output that "flattens" the nested structure from an indentation point of vi

Re: Buildinfo in the Debian archive, updates

2016-11-14 Thread Ximin Luo
Ximin Luo: > [..] > > Now then, why does the FTP archive need to distribute buildinfo files at all? > It can simply store the signed files and distribute the hashes. Then > rebuilders > (people that want to verify our reproducibility claims) can download the > hashes > from the archive, get the

Please review draft for week 81's blog post

2016-11-14 Thread Ximin Luo
https://reproducible.alioth.debian.org/blog/drafts/81/ Feel free to commit fixes directly to drafts/81.mdwn in https://anonscm.debian.org/git/reproducible/blog.git/ I will publish this in 24 hours. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/p

Bug#844343: golang-github-pierrec-lz4: FTBFS on armhf (TestCopy crashes)

2016-11-14 Thread Daniel Stender
Source: golang-github-pierrec-lz4 Version: 0.0~git20151216.222ab1f-1 Severity: serious Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org The build of this package break in the reprod

Buildinfo in the Debian archive, updates

2016-11-14 Thread Ximin Luo
This email is a summary of some discussions that happened after the last post to bug #763822, plus some more of my own thoughts and reasoning on the topic. I think having the Debian FTP archive distribute unsigned buildinfo files is an OK intermediate solution, with a few tweaks: 1. the hashes of

Re: Moving towards a deb-buildinfo(5) Format 1.0

2016-11-14 Thread Holger Levsen
On Mon, Nov 14, 2016 at 05:44:22AM +0900, Daniel Kahn Gillmor wrote: > >> Multiple builds of the same source package will set SOURCE_DATE_EPOCH to > >> the same value but will result in a different Build-Date. > It is definitely not what most of us initially expected, but it is > actually what we w

Bug#844303: ncrack: FTBFS: configure:6846: error: ./configure failed for opensshlib

2016-11-14 Thread Chris Lamb
Source: ncrack Version: 0.5-2 Severity: serious Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org Dear Maintainer, ncrack fails to build from source in unstable/amd64: […] | m

Bug#844301: arc-gui-clients: FTBFS: /usr/include/openssl/asn1_mac.h:10:2: error: #error "This file is obsolete; please update your software."

2016-11-14 Thread Chris Lamb
Source: arc-gui-clients Version: 0.4.6-3 Severity: serious Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org Dear Maintainer, arc-gui-clients fails to build from source in unstable/

Bug#844302: libapache-mod-musicindex: FTBFS: x86_64-linux-gnu-gcc: error: .specs: No such file or directory

2016-11-14 Thread Chris Lamb
Source: libapache-mod-musicindex Version: 1.4.1-1 Severity: serious Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org Dear Maintainer, libapache-mod-musicindex fails to build from s

Bug#844304: python-mysqldb: FTBFS: x86_64-linux-gnu-gcc: error: .specs: No such file or directory

2016-11-14 Thread Chris Lamb
Source: python-mysqldb Version: 1.3.7-1 Severity: serious Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org Dear Maintainer, python-mysqldb fails to build from source in unstable/am