[Reproducible-builds] Bug#789975: FTBFS: CMake Error at doc/doxygen .. INSTALL cannot find .. doc/doxygen/deal.tag
Source: deal.ii Version: 8.1.0-4 Severity: serious Tags: sid stretch Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: -- Installing: /tmp/buildd/deal.ii-8.1.0/debian/tmp/usr/share/doc/libdeal.ii-doc/LICENSE CMake Error at doc/doxygen/cmake_install.cmake:36 (file): file INSTALL cannot find /tmp/buildd/deal.ii-8.1.0/obj-x86_64-linux-gnu/doc/doxygen/deal.tag. Call Stack (most recent call first): doc/cmake_install.cmake:52 (include) cmake_install.cmake:39 (include) Makefile:88: recipe for target 'install' failed An example build log can be seen: https://reproducible.debian.net/rb-pkg/unstable/amd64/deal.ii.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#789977: FTBFS: missing dependency: network-uri =2.6
Package: git-repair Version: 1.20141027 Severity: serious Tags: sid stretch Justification: fails to build from source (but built successfully in the past) User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: [21 of 21] Compiling Main ( Setup.hs, Setup.o ) Linking Setup ... ../Setup configure checking version... 1.20141027 checking git... yes checking git version... 2.1.4 Configuring git-repair-1.20141027... Setup: At least the following dependencies are missing: network-uri =2.6 Makefile:10: recipe for target 'Build/SysConfig.hs' failed Alternative build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/git-repair.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#789978: FTBFS: lua5.2: test_discount.lua:49: attempt to index global 'lu' (a nil value)
Source: lua-discount Version: 1.2.10.1-1 Severity: serious Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build, during tests(?): Making target test for debian/lua5.2.dh-lua.conf ** lua dynamic (5.2) * Test: test_discount.lua lua5.2: test_discount.lua:49: attempt to index global 'lu' (a nil value) stack traceback: test_discount.lua:49: in main chunk [C]: in ? /usr/share/dh-lua/make/dh-lua.Makefile.single:288: recipe for target 'test-lua-dynamic-real' failed make[2]: *** [test-lua-dynamic-real] Error 1 /usr/share/dh-lua/make/dh-lua.Makefile.multiple:12: recipe for target 'test' failed Alternative build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/lua-discount.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#789991: FTBFS: Test failures including FixtureS.TestPanicOnSetUpSuite, FixtureS.TestPanicOnSetUpTest
Source: golang-gocheck Version: 0.0~bzr20131118+85-2 Severity: serious Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build during its tests: -- FAIL: fixture_test.go:132: FixtureS.TestPanicOnSetUpSuite fixture_test.go:153: c.Check(output.value, Matches, expected) value string = + \n + --\n + PANIC: gocheck_test.go:119: FixtureHelper.SetUpSuite\n + \n + ... Panic: SetUpSuite (PC=0x43A0F5)\n + \n + /usr/lib/go/src/runtime/asm_amd64.s:401\n + in call16\n + /usr/lib/go/src/runtime/panic.go:387\n + in gopanic\n + gocheck_test.go:109\n + in FixtureHelper.trace\n + gocheck_test.go:120\n + in FixtureHelper.SetUpSuite\n + /usr/lib/go/src/runtime/asm_amd64.s:401\n + in call16\n regex string = + ^\n + -+\n + PANIC: gocheck_test\\.go:[0-9]+: FixtureHelper.SetUpSuite\n + \n + \\.\\.\\. Panic: SetUpSuite \\(PC=[xA-F0-9]+\\)\n + \n + .+:[0-9]+\n + in panic\n + .*gocheck_test.go:[0-9]+\n + in FixtureHelper.trace\n + .*gocheck_test.go:[0-9]+\n + in FixtureHelper.SetUpSuite\n + .+:[0-9]+\n + in call[0-9]+\n + $ OOPS: 119 passed, 5 FAILED --- FAIL: Test (0.18s) FAIL exit status 1 FAILlaunchpad.net/gocheck 0.186s I can reproduce these five tests failing locally. Jenkins finds some benchmark tests failing too: https://reproducible.debian.net/rb-pkg/unstable/amd64/golang-gocheck.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] Storing .deb checksums in ADMINDIR/status?
Hi, Quoting Guillem Jover (2015-06-26 06:30:39) On Tue, 2015-06-23 at 09:31:05 +0200, Jérémy Bobbio wrote: Some people suggested that we should record a checksum of the `.deb` installed as a way to unambiguously referring to a specific package. In principle the tuple pkgname-version-arch should be unique per archive, otherwise bad-things-will-happen. Of course that does not cover locally built packages and similar, or mixing different archives with duplicated tuples, but then those are probably out-of-scope for reproducible builds *in* Debian anyway, I guess. I would like to second this. During my work on real dependency solvers, we need an answer to the question what makes a package unique and as Guillem already pointed out, a binary package is unique if it has the same packagename-version-arch tuple. In principal it would theoretically be possible to extend this definition by a fourth tuple member being a checksum of some sorts but that would mean that even more software like dpkg and apt would have to be adapted to follow this new definition of unique-ness. So instead of doing that I'd rather like if everybody building binary packages that could potentially end up being mixed with Debian packages would realize that *the name-ver-arch tuple they use for them must be unique*. If they don't manage to do that, then somebody should make them aware of the problem that packages are unique by the name-ver-arch tuple. Since David pointed out that this is a real problem, I think this issue might need more awareness. In summary, yes this could be solved technically but I'd rather prefer a social solution which spreads awareness about the unique-ness problem. cheers, josch signature.asc Description: signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#789940: FTBFS: gtk_widget_override_background_color is deprecated and -Werror
Source: libgrip Version: 0.3.8-1 Severity: serious Tags: sid stretch Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: gesture.c: In function ‘create_window’: gesture.c:219:3: error: ‘gtk_widget_override_background_color’ is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkwidget.h:1157) [-Werror=deprecated-declarations] gtk_widget_override_background_color (app-da, GTK_STATE_NORMAL, white); ^ cc1: all warnings being treated as errors An alternative build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/libgrip.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#789942: mapnik-vector-tile: FTBFS with mapnik 3.0(?): mapnik/graphics.hpp: No such file or directory
Package: mapnik-vector-tile Version: 0.5.1+dfsg-1.3 Severity: serious Tags: sid stretch Justification: fails to build from source (but built successfully in the past) User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build in sid: ake[2]: Entering directory '/mapnik-vector-tile-0.5.1+dfsg' echo #define MAPNIK_PLUGINDIR \/usr/lib/mapnik/3.0/input\ test/test-cfg.h In file included from test/vector_tile.cpp:6:0: test/test_utils.hpp:6:31: fatal error: mapnik/graphics.hpp: No such file or directory #include mapnik/graphics.hpp ^ compilation terminated. I believe this is due to libmapnik-dev pulling in mapnik 3.0. See also e.g. http://bugs.debian.org/788767 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/mapnik-vector-tile.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#789985: FTBFS: IRanges_defines.h: fatal error: S4Vectors_defines.h: No such file or directory
Package: r-bioc-shortread Version: 1.22.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: config.status: creating src/Makevars ** libs make[1]: Entering directory '/tmp/buildd/r-bioc-shortread-1.22.0/src' gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -I/usr/lib/R/site-library/IRanges/include -I/usr/lib/R/site-library/XVector/include -I/usr/lib/R/site-library/Biostrings/include -fopenmp -fpic -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -g -c Biostrings_stubs.c -o Biostrings_stubs.o In file included from /usr/lib/R/site-library/Biostrings/include/Biostrings_defines.h:18:0, from /usr/lib/R/site-library/Biostrings/include/Biostrings_interface.h:114, from /usr/lib/R/site-library/Biostrings/include/_Biostrings_stubs.c:1, from Biostrings_stubs.c:1: /usr/lib/R/site-library/IRanges/include/IRanges_defines.h:18:31: fatal error: S4Vectors_defines.h: No such file or directory #include S4Vectors_defines.h ^ compilation terminated. /usr/lib/R/etc/Makeconf:134: recipe for target 'Biostrings_stubs.o' failed Maybe this is a bug in r-bioc-biostrings, or r-bioc-iranges? The same bug affects at least r-bioc-genomicalignments, r-bioc-rtracklayer, and r-bioc-variantannotation. (all same maintainer) Full build log: https://reproducible.debian.net/rb-pkg/testing/amd64/r-bioc-shortread.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#789980: FTBFS: from pymongo import ... ImportError: cannot import name Connection
Source: python-mongoengine Version: 0.6.13-2 Severity: serious Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: make[2]: Entering directory '/tmp/buildd/python-mongoengine-0.6.13/docs.debian' sphinx-build -b html -d _build/doctrees . _build/html Making output directory... Running Sphinx v1.2.3 Exception occurred: File /tmp/buildd/python-mongoengine-0.6.13/mongoengine/connection.py, line 2, in module from pymongo import Connection, ReplicaSetConnection, uri_parser ImportError: cannot import name Connection The full traceback has been saved in /tmp/sphinx-err-ty4S2z.log, if you want to report the issue to the developers. Alternative build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/python-mongoengine.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#789981: wheel: please normalize timestamps in whl files
Source: wheel Version: 0.24.0-3 Severity: wishlist Tags: patch User: reproducible-builds@lists.alioth.debian.org Usertags: timestamps toolchain X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org Hi! Thanks for applying the reproducibility patch in one of the last uploads! :) We found another small issue about reproducibility of whl files (see [1]). The timestamps still vary depending on the configured timezone. The fix would be to store them in UTC like in the attached patch. Regards, Reiner [1]: https://reproducible.debian.net/rb-pkg/unstable/amd64/python-setuptools.html diff --git a/debian/patches/reproducible-whls.diff b/debian/patches/reproducible-whls.diff index 18c0372..3675e3f 100644 --- a/debian/patches/reproducible-whls.diff +++ b/debian/patches/reproducible-whls.diff @@ -30,7 +30,7 @@ Author: Barry Warsaw ba...@debian.org +if timestamp is None: +date_time = None +else: -+date_time = time.localtime(int(timestamp))[0:6] ++date_time = time.gmtime(int(timestamp))[0:6] + # XXX support bz2, xz when available zip = zipfile.ZipFile(open(zip_filename, wb+), w, @@ -44,7 +44,7 @@ Author: Barry Warsaw ba...@debian.org +def writefile(path, date_time): +if date_time is None: +st = os.stat(path) -+mtime = time.localtime(st.st_mtime) ++mtime = time.gmtime(st.st_mtime) +date_time = mtime[0:6] +zinfo = zipfile.ZipInfo(path, date_time) +with open(path, 'rb') as fp: signature.asc Description: OpenPGP digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#789989: FTBFS: The type TranslationUnit must implement [...] ITranslationUnit.getFile()
Source: eclipse-ptp
Version: 8.0.0-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
@dot:
[mkdir] Created dir:
/tmp/buildd/eclipse-ptp-8.0.0/debian/.eclipse-build/org.eclipse.ptp.rdt.core/@dot
[javac] Compiling 191 source files to
/tmp/buildd/eclipse-ptp-8.0.0/debian/.eclipse-build/org.eclipse.ptp.rdt.core/@dot
[javac] 470. ERROR in
/eclipse-ptp-8.0.0/debian/.eclipse-build/org.eclipse.ptp.rdt.core/src/org/eclipse/ptp/internal/rdt/core/model/TranslationUnit.java
(at line 62)
[javac] public class TranslationUnit extends Parent implements
ITranslationUnit {
[javac] ^^^
[javac] The type TranslationUnit must implement the inherited abstract
method ITranslationUnit.getFile()
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/eclipse-ptp.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#789946: FTBFS: Failed to resolve artifact. Missing: org.jruby.extras:jffi:jar:debian
Package: jenkins-instance-identity Version: 1.4-1 Severity: serious Tags: sid stretch Justification: fails to build from source (but built successfully in the past) User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build due to some unresolvable maven dependencies while maven is in offline mode: [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.jruby.extras:jffi:jar:debian [..] Path to dependency: 1) org.jenkins-ci.modules:instance-identity:jenkins-module:1.4 2) org.jenkins-ci.main:jenkins-core:jar:1.565.3 3) org.jruby.extras:jffi:jar:debian 2) org.jruby.ext.posix:jnr-posix:jar:debian [..] Path to dependency: 1) org.jenkins-ci.modules:instance-identity:jenkins-module:1.4 2) org.jenkins-ci.main:jenkins-core:jar:1.565.3 3) org.jruby.ext.posix:jnr-posix:jar:debian I remember something about there being a different named jruby dependency which provides these, but I'm /totally failing/ to find it anywhere. Alternative build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/jenkins-instance-identity.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#789943: FTBFS: Unable to parse version '=0.90 3.0' with dependency ruflin/elastica
Package: php-monolog
Version: 1.14.0-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source (but built successfully in the past)
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build in sid, but seems fine in testing (for now):
dh_phpcomposer
exception 'InvalidArgumentException' with message 'Unable to parse version
'=0.90 3.0' with dependency ruflin/elastica (=0.90 3.0)' in
/usr/share/php/pkgtools/phpcomposer/source.php:192
Stack trace:
#0 /usr/share/php/pkgtools/phpcomposer/command.php(73):
Pkgtools\Phpcomposer\Source-getDependencies()
#1 [internal function]: Pkgtools\Phpcomposer\Command-runSubstvars()
#2 /usr/share/php/pkgtools/base/command.php(180): call_user_func_array(Array,
Array)
#3 /usr/share/php/pkgtools/base/command.php(168):
Pkgtools\Base\Command-parseArgs(Array)
#4 /usr/bin/pkgtools(32): Pkgtools\Base\Command-parseArgs()
#5 {main}
Fuller log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/php-monolog.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#789963: qrfcview: please make the build reproducible
Source: qrfcview Version: 0.62-5.2 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 qrfcview could not be built reproducibly. The attached patch removes the timestamps from the the generated png icon. Once applied, qrfcview can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds -- Dhole diff -u qrfcview-0.62/debian/rules qrfcview-0.62/debian/rules --- qrfcview-0.62/debian/rules +++ qrfcview-0.62/debian/rules @@ -42,7 +42,7 @@ # Installation of icon and pixmap (hence imagemagick dependency). install -d -m 755 debian/qrfcview/usr/share/icons - convert -thumbnail 32x32 images/rfcview.png debian/qrfcview/usr/share/icons/qrfcview.png + convert -thumbnail 32x32 images/rfcview.png +set date:create +set date:modify -define png:exclude-chunk=time debian/qrfcview/usr/share/icons/qrfcview.png install -d -m 755 debian/qrfcview/usr/share/pixmaps convert -thumbnail 32x32 images/rfcview.png debian/qrfcview/usr/share/pixmaps/qrfcview.xpm diff -u qrfcview-0.62/debian/changelog qrfcview-0.62/debian/changelog --- qrfcview-0.62/debian/changelog +++ qrfcview-0.62/debian/changelog @@ -1,3 +1,10 @@ +qrfcview (0.62-6) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Remove timestamp from png to make package build reproducibly + + -- Dhole dh...@openmailbox.org Thu, 25 Jun 2015 16:53:17 +0200 + qrfcview (0.62-5.2) unstable; urgency=low * Non-maintainer upload. signature.asc Description: OpenPGP digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#789964: xutils-dev: please make the build reproducible
Source: xutils-dev Version: 1:7.7+3 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 xutils-dev makes some packages not build reproducibly. The attached patch modifies the default GzipCmd used in Imake from 'gzip' to 'gzip -n' so that timestamps are not stored in packages that use functions depending on GzipCmd. Once applied, xtel (and maybe others) can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds -- Dhole diff -Nru xutils-dev-7.7+3/debian/changelog xutils-dev-7.7+3.1/debian/changelog --- xutils-dev-7.7+3/debian/changelog 2014-05-21 21:46:36.0 +0200 +++ xutils-dev-7.7+3.1/debian/changelog 2015-06-25 18:12:12.0 +0200 @@ -1,3 +1,11 @@ +xutils-dev (1:7.7+3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Change default GzipCmd to `gzip -n` so that packages depending on +xutils-dev can be built reproducibly + + -- Dhole dh...@openmailbox.org Thu, 25 Jun 2015 18:11:15 +0200 + xutils-dev (1:7.7+3) unstable; urgency=medium * gccmakedep 1.0.3. diff -Nru xutils-dev-7.7+3/xorg-cf-files/Imake.tmpl xutils-dev-7.7+3.1/xorg-cf-files/Imake.tmpl --- xutils-dev-7.7+3/xorg-cf-files/Imake.tmpl 2014-05-21 21:01:41.0 +0200 +++ xutils-dev-7.7+3.1/xorg-cf-files/Imake.tmpl 2015-06-25 18:09:25.0 +0200 @@ -1190,7 +1190,7 @@ #define CompressCmd compress #endif #ifndef GzipCmd -#define GzipCmd gzip +#define GzipCmd gzip -n #endif #ifndef CppCmd #define CppCmd /LibDirName/cpp signature.asc Description: OpenPGP digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#789965: xtel: please make the build reproducible
Source: xtel Version: 3.3.0-17.1 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 xtel could not be built reproducibly. The attached patch removes extra timestamps from compressed files by gzip and from the png icon. Once applied, and with a patched version of the dependency xutils-dev, xtel can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds -- Dhole diff -u xtel-3.3.0/debian/changelog xtel-3.3.0/debian/changelog --- xtel-3.3.0/debian/changelog +++ xtel-3.3.0/debian/changelog @@ -1,3 +1,11 @@ +xtel (3.3.0-17.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Don't store timestamps when calling gzip and remove timestamps from png +to make package build reproducibly + + -- Dhole dh...@openmailbox.org Thu, 25 Jun 2015 16:30:25 +0200 + xtel (3.3.0-17.1) unstable; urgency=medium * Non-maintainer upload. diff -u xtel-3.3.0/debian/rules xtel-3.3.0/debian/rules --- xtel-3.3.0/debian/rules +++ xtel-3.3.0/debian/rules @@ -20,7 +20,7 @@ xmkmf make Xtel # convert the mean gif file into a png file - convert xtel.gif xtel.png + convert xtel.gif +set date:create +set date:modify -define png:exclude-chunk=time xtel.png touch build-stamp clean: @@ -62,7 +62,7 @@ install -m 644 LISEZMOI.txt debian/xtel/usr/share/doc/LANG/fr/xtel/ install -m 644 FAQ.txt debian/xtel/usr/share/doc/LANG/fr/xtel/ install -m 644 README_IMINITEL.txt debian/xtel/usr/share/doc/LANG/fr/xtel/ - gzip -9v debian/xtel/usr/share/doc/LANG/fr/xtel/*.txt + gzip -9vn debian/xtel/usr/share/doc/LANG/fr/xtel/*.txt # Install png image example install -m 644 xtel.png debian/xtel/usr/share/doc/xtel/ # Create a symlink in /usr/share/doc/xtel to the french doc directory signature.asc Description: OpenPGP digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] Bug#789648: Bug#789648: apt-dater: please make the build reproducible
tags 789648 fixed-upstream thanks Hi, On 06/23/2015 11:06 AM, Ximin Luo wrote: On 23/06/15 03:42, Dhole wrote: While working on the “reproducible builds” effort [1], we have noticed that apt-dater could not be built reproducibly. Hi, Please see https://wiki.debian.org/ReproducibleBuilds/TimestampsProposal We decided to standardise SOURCE_DATE_EPOCH for this sort of thing. help2man(1) already supports it, see #787444. At some point we will get debhelper to set this automatically. I haven't looked at the patch, but I imagine it should be straightforward to s/BUILD_DATE/SOURCE_DATE_EPOCH. I've changed the sources to use SOURCE_DATE_EPOCH has reference. The string embedded into the version info is build using the reference timestamp in UTC. Maybe there should be a SOURCE_DATE_UTC build from SOURCE_DATE_EPOCH using `date ... -u` since RFC2822 contains a timezone making reproducible builds hard. $ date -d $(dpkg-parsechangelog --count 1 -SDate) Tue Jun 16 11:43:42 CEST 2015 $ export SOURCE_DATE_EPOCH=$(date -d $(dpkg-parsechangelog --count 1 -SDate) +%s) $ date -d @$SOURCE_DATE_EPOCH -u Tue Jun 16 09:43:42 UTC 2015 $ ./src/apt-dater -v apt-dater 1.0.2 - Tue Jun 16 09:43:42 UTC 2015 The upstream part is fine but adding SOURCE_DATE_EPOCH in debian/rules ist still missing. HTH, Thomas (upstream) -- supp...@ibh.de Tel. +49 351 477 77 30 www.ibh.de Fax +49 351 477 77 39 --- Dipl.-Ing. Thomas Liske Netzwerk- und System-Design IBH IT-Service GmbH Amtsgericht Dresden Gostritzer Str. 67a HRB 13626 D-01217 Dresden GF: Prof. Dr. Thomas Horn Germany VAT DE182302907 --- Ihr Partner für: LAN, WAN IP-Quality, Security, VoIP, SAN, Backup, USV --- professioneller IT-Service - kompetent und zuverlässig --- signature.asc Description: OpenPGP digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#789997: python-pysqlite2: [PATCH] please make the build reproducible
Package: python-pysqlite2 Version: 2.6.3-3 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 python-pysqlite2 could not be built reproducibly. The attached patches removes extra timestamps from the build system. Once applied, python-pysqlite2 can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds diff -urNp python-pysqlite2-2.6.3.old/debian/rules python-pysqlite2-2.6.3/debian/rules --- python-pysqlite2-2.6.3.old/debian/rules 2012-06-24 08:14:37.0 + +++ python-pysqlite2-2.6.3/debian/rules 2015-06-26 02:12:28.077796703 + @@ -8,6 +8,10 @@ include /usr/share/dpkg/buildflags.mk PYVERS = $(shell pyversions -r) +LAST_CHANGE = $(shell dpkg-parsechangelog -S Date) +BUILD_DATE = $(shell LC_ALL=C date -u +%B %d, %Y -d $(LAST_CHANGE)) +SPHINXOPTS := -D html_last_updated_fmt=\$(BUILD_DATE)\ + build: build-arch build-indep build-arch: build-stamp build-indep: build-stamp @@ -60,7 +64,7 @@ binary-indep: dh_prep dh_installdirs -i usr/share/doc/python-pysqlite2-doc/html - python setup.py build_docs + python setup.py build_docs --sphinxopts=$(SPHINXOPTS) dh_installdocs -i build/doc/* cd debian/python-pysqlite2-doc/usr/share/doc/python-pysqlite2-doc \ mv *.html *.js *.inv _static _sources html \ Description: Modify DocBuilder command Modify DocBuilder command to use sphinxopts command line option for add parameters in the call to sphinx-build. Author: Juan Picca jumap...@gmail.com Last-Update: 2015-06-25 --- --- a/setup.py +++ b/setup.py @@ -65,10 +65,10 @@ else: class DocBuilder(Command): description = Builds the documentation -user_options = [] +user_options = [(sphinxopts=, None, sphinx options)] def initialize_options(self): -pass +self.sphinxopts = def finalize_options(self): pass @@ -80,7 +80,7 @@ class DocBuilder(Command): except OSError: pass os.makedirs(build/doc) -rc = os.system(sphinx-build doc/sphinx build/doc) +rc = os.system(sphinx-build %s doc/sphinx build/doc % self.sphinxopts) if rc != 0: print Is sphinx installed? If not, try 'sudo easy_install sphinx'. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] Storing .deb checksums in ADMINDIR/status?
Hi! On Tue, 2015-06-23 at 09:31:05 +0200, Jérémy Bobbio wrote: Some people suggested that we should record a checksum of the `.deb` installed as a way to unambiguously referring to a specific package. In principle the tuple pkgname-version-arch should be unique per archive, otherwise bad-things-will-happen. Of course that does not cover locally built packages and similar, or mixing different archives with duplicated tuples, but then those are probably out-of-scope for reproducible builds *in* Debian anyway, I guess. The main benefit that I can think of is that it would allow to directly retrieve the file from snapshot.debian.org based on the hash‗[2]. Personally I find the point that David mentioned to be a bit more interesting. :) But, as far as I know, this information is currently not recorded by dpkg and there is no way to know for sure which `.deb` has been used for a package currently installed. I have a couple of memories where this could have been useful outside of the aforementioned use case. · From my limited knowledge of dpkg's internals, computing checksums and adding a new field to the status file doesn't seem hard to implement. The general idea seems worthwhile in principle. The devil is in the details though, and with dpkg, the implementation is usually not the hard part. :) David also pointed some of the possible issues. Others that quickly come to mind, would be: * Checksum of what exactly? Although the seemingly obvious answer might be “the entire .deb container”, depending on what one wants, the interesting data might be different. For example, essential for apt would appear to be control.tar and data.tar, and you might not want to reinstall if some other member changes; when using signed packages changes to the signatures might also be relevant. Other .deb members might also be relevant in case another tool wants to use them. * Currently dpkg extracts the control.tar with dpkg-deb directly to disk, and gets the data.tar contents piped from dpkg-deb, so it does not get direct access to the whole file, which means the checksum would need to be computed out-of-band, needing to process the .deb one more time, which might be wasteful. * A possibility could be to pre-compute the checksum on creation or modification time, and store it in the debian-binary member for example. The problem with that is that tools that modify .debs might not genereate a checksum, or worse might not update it. And this would also not benefit old binaries. * Another possibility might be to make dpkg-deb compute the checksum when parsing the .deb and output it on a supplied fd through a command-line option. * Even when dpkg was being used through dselect, where the checksums from the archive were fresh and at reach from the available file, dpkg has never propagated them to the status file. I guess mainly because at the time of «dpkg -i», there was no guarantee that those packages corresponded to the ones from the archive. … Thanks, Guillem ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
