Re: [Reproducible-builds] [coreboot] coreboot reproducible builds almost there
Dear coreboot folks, Am Donnerstag, den 26.02.2015, 17:23 +0200 schrieb Emilian Bold: > I was trying to duplicate a coreboot build back in November and I noticed I > couldn't get my ROM file to be identical to the one I found online. > > It seems that coreboot doesn't have reproducible builds yet. > > Debian has been looking into this for a while > https://wiki.debian.org/ReproducibleBuilds and I think coreboot should > adopt this concept. […] Holger Levsen joined #coreb...@irc.freenode.net yesterday to report that he integrated coreboot into the reproducible builds infrastructure [1]. After configuring the used build script [2] to build without a payload, nice ionice -c 3 \ bash util/abuild/abuild --payloads none || true # don't fail the full job just because some targets fail it looks like most boards are passing the test now [1]. Big thanks to Alexander (lynxis) for submitting the necessary patches! The only exceptions are the six boards below. * a-trend_atc-6220 (256K) is unreproducible. * a-trend_atc-6240 (256K) is unreproducible. * google_nyan (4096K) is unreproducible. * google_nyan_big (4096K) is unreproducible. * google_rush (4096K) is unreproducible. * google_rush_ryu (8192K) is unreproducible. Also, as a side node, SeaBIOS also supports to be built reproducible since commit 624e8127 (build: Support "make VERSION=xyz" to override the default build version) [3], though not by default. So the coreboot build system, building the SeaBIOS payload, would need to be adapted, if a reproducible build with the SeaBIOS payload is required. Thanks, Paul [1] https://reproducible.debian.net/coreboot/coreboot.html [2] http://anonscm.debian.org/cgit/qa/jenkins.debian.net.git/tree/bin/reproducible_coreboot.sh [3] http://seabios.org/pipermail/seabios/2015-June/009253.html signature.asc Description: This is a digitally signed message part ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] [coreboot] coreboot reproducible builds almost there
Dear coreboot folks, adding the Debian reproducible-builds lists to cc: - please either cc: that list or me on replies, i'm not subscribed to the coreboot list. On Donnerstag, 11. Juni 2015, Paul Menzel wrote: > Holger Levsen joined #coreb...@irc.freenode.net yesterday to report that > he integrated coreboot into the reproducible builds infrastructure [1]. indeed :) Thanks for sharing this here! I'm now wondering how to proceed further. I *believe* another set of tests, this time with payloads, would be useful, if only to prove that the combination "reproducible coreboot" plus "reproducible payload" also is reproducible. Things is, _AIUI_, there is no common payload which can be enabled for all boards. Is that correct? If it is, is there another way to sensible group targets by payloads or detect sensible ones? Currently I'm building all targets in one pass using abuild, but I could also loop through each target and build it individually, as long as I dont have to configure 247 different configurations... (rather easy would be, all i386 targets use seabios, all mips target $that_one and all arm targets $another_one... And then I'm wondering, "what next"? AIUI you don't ever offer images for download and instead expect users to build coreboot themselves. So the whole topic of verifying and reproducing the vendors (=your!) binaries is a bit mood here, at least atm. Any comments on that? Last, and probably least: currently the headline of the page says "fast, flexible and reproducible Open Source firmware_?_" which I felt was appropriate when only a few images with payload were reproducible. Now I've been thinking about removing the questionmark, but in a way I like to keep it, til you reached 100% (without payloads) - do you think thats "ok"? IOW: do you feel offended (or maybe just a bit "hmm") by the questionmark or do you see it as motivation (to reach 100%)? ;-) Oh, and as the page says, it's currently only updated once a month and on demand, so please do ping me if you merged some reproducible changes into master! Thanks for your work on coreboot - it's really awesome & amazing! Free the hardware! :-) cheers, Holger, happy about any feedback basically. coreboot.html is *your* page, not mine! :-) signature.asc Description: This is a digitally signed message part. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] ruby-celluloid: tests run forever
control: reopen -1
Hi Cedric,
unfortunatly ruby-celluloid still fails to build in the
reproducible.debian.net setup, it hung for 24h here until I killed it:
Running tests for ruby2.1 using debian/ruby-tests.rake ...
RUBYLIB=/tmp/buildd/ruby-celluloid-0.16.0/debian/ruby-
celluloid/usr/lib/ruby/vendor_ruby:. GEMPATH= ruby2.1 -rrake -e
ARGV.unshift\(\"-f\",\ \"debian/ruby-tests.rake\"\)\;\ Rake.application.run
/usr/bin/ruby2.1 -S rspec ./spec/celluloid/actor_spec.rb
./spec/celluloid/actor_system_spec.rb ./spec/celluloid/block_spec.rb
./spec/celluloid/calls_spec.rb ./spec/celluloid/condition_spec.rb
./spec/celluloid/cpu_counter_spec.rb ./spec/celluloid/evented_mailbox_spec.rb
./spec/celluloid/fsm_spec.rb ./spec/celluloid/future_spec.rb
./spec/celluloid/internal_pool_spec.rb ./spec/celluloid/links_spec.rb
./spec/celluloid/logging/ring_buffer_spec.rb ./spec/celluloid/mailbox_spec.rb
./spec/celluloid/notifications_spec.rb ./spec/celluloid/pool_spec.rb
./spec/celluloid/probe_spec.rb ./spec/celluloid/properties_spec.rb
./spec/celluloid/registry_spec.rb ./spec/celluloid/stack_dump_spec.rb
./spec/celluloid/supervision_group_spec.rb ./spec/celluloid/supervisor_spec.rb
./spec/celluloid/tasks/task_fiber_spec.rb
./spec/celluloid/tasks/task_thread_spec.rb
./spec/celluloid/thread_handle_spec.rb ./spec/celluloid/timer_spec.rb
./spec/celluloid/uuid_spec.rb
Run options: include {:focus=>true}
All examples were filtered out; ignoring {:focus=>true}
...FTerminated
++ cleanup_all
Terminated
Full log available at
https://jenkins.debian.net/view/reproducible/job/reproducible_builder_beta/50735/console
Feel free to downgrade the severity if you think this could be related /
specific to the jenkins.dn setup!
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] cheers to ikiwiki
hey Reproducible Build folks--
Just wanted to give a shout out to Simon McVittie (cc'ed here), who did
a bunch of work getting ikiwiki to support a deterministic option.
In ikiwiki version 3.20150610, we see the following
reproducibility-oriented changes (in addition to a small fix i supplied
for #785738):
* Populate pagectime from either mtime or inode change time,
whichever is older, again for more reproducible builds
* debian: build the docwiki with LC_ALL=C.UTF-8 and TZ=UTC
* brokenlinks: sort the pages that link to the missing page, for
better reproducibility
* Add [[!meta date]] to news items and tips, since the git checkout
and build process can leave the checkout date in the tarball
release, leading to unstable sorting
* Sort backlinks deterministically, by falling back to sorting by href
if the link text is identical
* Add a $config{deterministic} option and use it for the docwiki
* haiku: if deterministic build is requested, return a hard-coded haiku
* polygen: if deterministic build is requested, use a well-known random
seed
Thanks to Simon for all this thoughtful tuning of a rather intricate
package. It's much appreciated!
Regards,
--dkg
signature.asc
Description: PGP 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#788467: astroquery: [PATCH] please make the build reproducible
Package: astroquery Version: 0.2.4+dfsg-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 astroquery could not be built reproducibly. The attached patch removes extra timestamps from the build system. Once applied, astroquery can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds diff -urNp astroquery-0.2.4+dfsg.old/debian/rules astroquery-0.2.4+dfsg/debian/rules --- astroquery-0.2.4+dfsg.old/debian/rules 2015-04-07 06:53:09.0 -0300 +++ astroquery-0.2.4+dfsg/debian/rules 2015-06-11 09:10:16.195865837 -0300 @@ -6,12 +6,16 @@ export PYBUILD_TEST_PYTEST=1 export PYBUILD_TEST_ARGS=../../../astroquery export http_proxy=127.0.0.1:9 +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)" + %: dh $@ --with python2,python3,sphinxdoc --buildsystem=pybuild override_dh_auto_build: dh_auto_build - PYTHONPATH=. sphinx-build -N -bhtml docs/ build/html # HTML generator + PYTHONPATH=. sphinx-build $(SPHINXOPTS) -N -bhtml docs/ build/html # HTML generator override_dh_auto_clean: dh_auto_clean ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#788469: glance: [PATCH] please make the build reproducible
Package: glance Version: 2015.1.0-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 glance could not be built reproducibly. The attached patch removes extra timestamps from the build system. Once applied, glance can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds diff -urNp glance-2015.1.0.old/debian/rules glance-2015.1.0/debian/rules --- glance-2015.1.0.old/debian/rules 2015-04-30 18:46:13.0 -0300 +++ glance-2015.1.0/debian/rules 2015-06-11 09:29:37.859893246 -0300 @@ -6,6 +6,11 @@ include /usr/share/openstack-pkg-tools/p export OSLO_PACKAGE_VERSION=$(VERSION) +LAST_CHANGE = $(shell dpkg-parsechangelog -S Date) +BUILD_DATE = $(shell LC_ALL=C date -u "+%B %d, %Y" -d "$(LAST_CHANGE)") +SPHINXOPTS := -D today="$(BUILD_DATE)" +SPHINXOPTS += -D html_last_updated_fmt="$(BUILD_DATE)" + %: dh $@ --buildsystem=python_distutils --with python2,sphinxdoc,systemd @@ -25,13 +30,13 @@ override_dh_auto_build: override_dh_sphinxdoc: ifeq (,$(findstring nodocs, $(DEB_BUILD_OPTIONS))) - sphinx-build -b html doc/source $(CURDIR)/debian/python-glance-doc/usr/share/doc/python-glance-doc/html + sphinx-build $(SPHINXOPTS) -b html doc/source $(CURDIR)/debian/python-glance-doc/usr/share/doc/python-glance-doc/html dh_sphinxdoc -O--buildsystem=python_distutils endif override_dh_installman: ifeq (,$(findstring nodocs, $(DEB_BUILD_OPTIONS))) - sphinx-build -b man doc/source doc/build/man + sphinx-build $(SPHINXOPTS) -b man doc/source doc/build/man dh_installman -O--buildsystem=python_distutils endif ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#788476: mpi4py: [PATCH] please make the build reproducible
Package: mpi4py
Version: 1.3.1+hg20131106-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 mpi4py could not be built reproducibly.
The attached patch removes extra timestamps from the build system.
Once applied, mpi4py can be built reproducibly in our current experimental
framework.
[1]: https://wiki.debian.org/ReproducibleBuilds
diff -urNp mpi4py-1.3.1+hg20131106.old/debian/rules mpi4py-1.3.1+hg20131106/debian/rules
--- mpi4py-1.3.1+hg20131106.old/debian/rules 2014-11-24 12:21:30.0 -0200
+++ mpi4py-1.3.1+hg20131106/debian/rules 2015-06-11 09:35:09.259901065 -0300
@@ -8,6 +8,9 @@ PY3VERS = $(shell py3versions -vr)
CYTHON_VER := $(shell dpkg -l cython 2>/dev/null | awk '/^ii/{print $$3;}' || echo 0)
RECONF = $(shell dpkg --compare-versions $(CYTHON_VER) ge 0.19.1 && echo ",autoreconf" || echo "")
+LAST_CHANGE = $(shell dpkg-parsechangelog -S Date)
+BUILD_DATE = $(shell LC_ALL=C date -u "+%B %d, %Y" -d "$(LAST_CHANGE)")
+
# Specify a specific version of MPI to use in the build, otherwise
# just use the default.
# MPI=.openmpi
@@ -40,7 +43,7 @@ override_dh_auto_build:
: # Build documentation now
PYTHONPATH=`/bin/ls -d $(CURDIR)/build/lib.*$(PY2)` \
- make -C docs/source/usrman/ html
+ make -C docs/source/usrman/ html SPHINXOPTS="-D today=\"$(BUILD_DATE)\""
override_dh_auto_install:
dh_auto_install
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#788477: musicbrainzngs: [PATCH] please make the build reproducible
Package: musicbrainzngs Version: 0.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 musicbrainzngs could not be built reproducibly. The attached patch removes extra timestamps from the build system. ensure a stable file order when creating the source archive. Once applied, musicbrainzngs can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds diff -urNp musicbrainzngs-0.5.old/debian/rules musicbrainzngs-0.5/debian/rules --- musicbrainzngs-0.5.old/debian/rules 2014-10-12 18:28:41.0 -0200 +++ musicbrainzngs-0.5/debian/rules 2015-06-11 09:50:54.495923368 -0300 @@ -4,12 +4,16 @@ #export DH_VERBOSE=1 export PYBUILD_NAME=musicbrainzngs + +LAST_CHANGE = $(shell dpkg-parsechangelog -S Date) +BUILD_DATE = $(shell LC_ALL=C date -u "+%B %d, %Y" -d "$(LAST_CHANGE)") + %: dh $@ --with python2,python3,sphinxdoc --buildsystem=pybuild override_dh_auto_build: dh_auto_build - make -C docs html + make -C docs html SPHINXOPTS="-D html_last_updated_fmt=\"$(BUILD_DATE)\"" override_dh_clean: rm -rf docs/_build ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#788478: ns3: [PATCH] please make the build reproducible
Package: ns3 Version: 3.22+dfsg-1 Severity: wishlist Template taken from https://wiki.debian.org/ReproducibleBuilds/Contribute Tags: patch User: reproducible-builds@lists.alioth.debian.org Usertags: timestamps Hi! While working on the "reproducible builds" effort [1], we have noticed that ns3 could not be built reproducibly. The attached patch removes extra timestamps from the build system. Once applied, ns3 can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds diff -urNp ns3-3.22+dfsg.old/debian/rules ns3-3.22+dfsg/debian/rules --- ns3-3.22+dfsg.old/debian/rules 2015-05-14 02:08:16.0 -0300 +++ ns3-3.22+dfsg/debian/rules 2015-06-11 10:05:28.687943994 -0300 @@ -14,15 +14,20 @@ BUILD_OPTION=$(shell if [ $(MEMORY) -lt CPU_CORES=$(shell nproc) BUILD_OPTION_OPTIPNG=$(shell echo "-j$(CPU_CORES)") +LAST_CHANGE = $(shell dpkg-parsechangelog -S Date) +BUILD_DATE = $(shell LC_ALL=C date -u "+%B %d, %Y" -d "$(LAST_CHANGE)") +SPHINXOPTS := -D today=\"$(BUILD_DATE)\" +SPHINXOPTS += -D html_last_updated_fmt=\"$(BUILD_DATE)\" + %: dh $@ --with python2 build-indep: build-doc-stamp build-doc-stamp: - make html man -C ./$(NS3_DIR)/doc/manual/ - make html man -C ./$(NS3_DIR)/doc/models/ - make html man -C ./$(NS3_DIR)/doc/tutorial/ + make html man -C ./$(NS3_DIR)/doc/manual/ SPHINXOPTS="$(SPHINXOPTS)" + make html man -C ./$(NS3_DIR)/doc/models/ SPHINXOPTS="$(SPHINXOPTS)" + make html man -C ./$(NS3_DIR)/doc/tutorial/ SPHINXOPTS="$(SPHINXOPTS)" rm ns-3.*/doc/*/build/*/_static/jquery.js rm ns-3.*/doc/*/build/*/_static/underscore.js touch $@ ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#788479: oslo-config: [PATCH] please make the build reproducible
Package: oslo-config Version: 1.9.3-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 oslo-config could not be built reproducibly. The attached patch removes extra timestamps from the build system. Once applied, oslo-config can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds diff -urNp oslo-config-1.9.3.old/debian/rules oslo-config-1.9.3/debian/rules --- oslo-config-1.9.3.old/debian/rules 2015-04-27 06:02:17.0 -0300 +++ oslo-config-1.9.3/debian/rules 2015-06-11 11:22:23.656052882 -0300 @@ -5,6 +5,10 @@ PYTHON3S:=$(shell py3versions -vr) UPSTREAM_GIT = git://github.com/openstack/oslo.config.git +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)" + include /usr/share/openstack-pkg-tools/pkgos.make export OSLO_PACKAGE_VERSION=$(VERSION) @@ -40,7 +44,7 @@ endif override_dh_sphinxdoc: ifeq (,$(findstring nodocs, $(DEB_BUILD_OPTIONS))) - sphinx-build -b html doc/source $(CURDIR)/debian/python-oslo.config-doc/usr/share/doc/python-oslo.config-doc/html + sphinx-build $(SPHINXOPTS) -b html doc/source $(CURDIR)/debian/python-oslo.config-doc/usr/share/doc/python-oslo.config-doc/html dh_sphinxdoc -O--buildsystem=python_distutils endif ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#788480: oslo.messaging: [PATCH] please make the build reproducible
Package: oslo.messaging Version: 1.8.1-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 oslo.messaging could not be built reproducibly. The attached patch removes extra timestamps from the build system. Once applied, oslo.messaging can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds diff -urNp oslo.messaging-1.8.1.old/debian/rules oslo.messaging-1.8.1/debian/rules --- oslo.messaging-1.8.1.old/debian/rules 2015-04-27 10:22:53.0 -0300 +++ oslo.messaging-1.8.1/debian/rules 2015-06-11 12:19:38.436133925 -0300 @@ -1,5 +1,9 @@ #!/usr/bin/make -f +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)" + include /usr/share/openstack-pkg-tools/pkgos.make export OSLO_PACKAGE_VERSION=$(VERSION) @@ -18,6 +22,6 @@ endif override_dh_sphinxdoc: ifeq (,$(findstring nodocs, $(DEB_BUILD_OPTIONS))) - sphinx-build -b html doc/source $(CURDIR)/debian/python-oslo.messaging/usr/share/doc/python-oslo.messaging/html + sphinx-build $(SPHINXOPTS) -b html doc/source $(CURDIR)/debian/python-oslo.messaging/usr/share/doc/python-oslo.messaging/html dh_sphinxdoc -O--buildsystem=python_distutils endif ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#788486: pyopencl: [PATCH] please make the build reproducible
Package: pyopencl Version: 2015.1-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 pyopencl could not be built reproducibly. The attached patch removes extra timestamps from the build system. Once applied, pyopencl can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds diff -urNp pyopencl-2015.1.old/debian/rules pyopencl-2015.1/debian/rules --- pyopencl-2015.1.old/debian/rules 2015-06-09 18:08:24.0 -0300 +++ pyopencl-2015.1/debian/rules 2015-06-11 12:26:35.960143776 -0300 @@ -12,6 +12,8 @@ endif LAST_CHANGE=$(shell dpkg-parsechangelog -S Date) BUILD_DATE=$(shell LC_ALL=C date -u "+%B %d, %Y" -d "$(LAST_CHANGE)") +SPHINXOPTS:=-D today=\"$(BUILD_DATE)\" +SPHINXOPTS+=-D html_last_updated_fmt=\"$(BUILD_DATE)\" %: dh $@ --with python2,python3,sphinxdoc @@ -50,7 +52,7 @@ override_dh_auto_install: override_dh_installdocs: # Required to build PyOpenCL symbols for documentation cp -Ri pyopencl.egg-info build/lib.*-*-$(firstword $(PYTHON2))/ - PYTHONPATH=../$$(ls -d build/lib.*-*-$(firstword $(PYTHON2)))/ $(MAKE) -C doc html SPHINXOPTS='-D today="$(BUILD_DATE)"' + PYTHONPATH=../$$(ls -d build/lib.*-*-$(firstword $(PYTHON2)))/ $(MAKE) -C doc html SPHINXOPTS="$(SPHINXOPTS)" rm -rf build/lib.*-*-$(firstword $(PYTHON2))/pyopencl.egg-info dh_installdocs ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#788487: python-amqp: [PATCH] please make the build reproducible
Package: python-amqp Version: 1.4.6-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 python-amqp could not be built reproducibly. The attached patch removes extra timestamps from the build system. Once applied, python-amqp can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds diff -urNp python-amqp-1.4.6.old/debian/rules python-amqp-1.4.6/debian/rules --- python-amqp-1.4.6.old/debian/rules 2015-05-19 06:47:20.0 -0300 +++ python-amqp-1.4.6/debian/rules 2015-06-11 12:36:32.040157840 -0300 @@ -3,6 +3,9 @@ # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 +LAST_CHANGE=$(shell dpkg-parsechangelog -S Date) +BUILD_DATE=$(shell LC_ALL=C date -u "+%B %d, %Y" -d "$(LAST_CHANGE)") + export PYBUILD_NAME=amqp %: @@ -10,7 +13,7 @@ export PYBUILD_NAME=amqp override_dh_auto_build: dh_auto_build - PYTHONPATH=. sphinx-build -b html -N docs/ docs/.build/html + PYTHONPATH=. sphinx-build -D today="$(BUILD_DATE)" -b html -N docs/ docs/.build/html override_dh_clean: rm -rf docs/.build ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] [coreboot] coreboot reproducible builds almost there
2015-06-11 10:25 GMT+02:00 Holger Levsen : > I'm now wondering how to proceed further. I *believe* another set of tests, > this time with payloads, would be useful, if only to prove that the > combination "reproducible coreboot" plus "reproducible payload" also is > reproducible. > > Things is, _AIUI_, there is no common payload which can be enabled for all > boards. Is that correct? The one that should run everywhere is Google's depthcharge, and that isn't hooked up to the build system like SeaBIOS is (and even depthcharge isn't available for emulation/qemu-riscv). So you're correct, there is no single payload for every board. > If it is, is there another way to sensible group targets by payloads or detect > sensible ones? Currently I'm building all targets in one pass using abuild, > but I could also loop through each target and build it individually, as long > as I dont have to configure 247 different configurations... (rather easy would > be, all i386 targets use seabios, all mips target $that_one and all arm > targets $another_one... Since we select default payloads in our Kconfig rules (seabios for x86), I guess we should start doing the same for other architectures. I don't think that belongs in your test script - things might change in the future, and that shouldn't require additional effort on your part. We'll work on that, and will tell you once there's a plan and/or implementation. > And then I'm wondering, "what next"? AIUI you don't ever offer images for > download and instead expect users to build coreboot themselves. So the whole > topic of verifying and reproducing the vendors (=your!) binaries is a bit mood > here, at least atm. Any comments on that? There are distributions, sort of. Google ships coreboot as part of Chrome OS (which requires a huge build system even to build just coreboot). Then there's libreboot (www.libreboot.org), which ships their coreboot-variant (without blobs and with as few patches against coreboot as possible) with GRUB2 as payload for a small selection of boards that they can support. There are also some other vendors, but they're less visible. If you want to support coreboot distributions (that ship binaries), libreboot is currently your best bet. > Last, and probably least: currently the headline of the page says "fast, > flexible and reproducible Open Source firmware_?_" which I felt was > appropriate when only a few images with payload were reproducible. Oh, I loved it, still do! At some point we should replace the question mark with an exclamation mark, though :-) > Oh, and as the page says, it's currently only updated once a month and on > demand, so please do ping me if you merged some reproducible changes into > master! Thanks, will do. Let's start immediately :-) Since you mentioned 'once we reach 100% (without payloads)' earlier: the issue of the remaining 7 non-reproducible board should be fixed since today, in response to your report. I'd appreciate if you could do another run to verify this. Regards, Patrick ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#788501: python-fudge: [PATCH] please make the build reproducible
Package: python-fudge Version: 1.0.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-fudge could not be built reproducibly. The attached patch removes extra timestamps from the build system. Once applied, python-fudge can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds diff -urNp python-fudge-1.0.3.old/debian/rules python-fudge-1.0.3/debian/rules --- python-fudge-1.0.3.old/debian/rules 2012-05-04 16:13:56.0 -0300 +++ python-fudge-1.0.3/debian/rules 2015-06-11 22:05:58.692513453 -0300 @@ -1,12 +1,16 @@ #!/usr/bin/make -f +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)" + override_dh_auto_clean: rm -rf build fudge.egg-info find -name '._*' -delete dh_auto_clean override_dh_auto_install: - sphinx-build -b html -a -c docs docs \ + sphinx-build $(SPHINXOPTS) -b html -a -c docs docs \ $(CURDIR)/debian/python-fudge-doc/usr/share/doc/python-fudge-doc/html python setup.py install --install-layout=deb \ --root $(CURDIR)/debian/python-fudge ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#788502: python-glance-store: [PATCH] please make the build reproducible
Package: python-glance-store Version: 0.4.0-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 python-glance-store could not be built reproducibly. The attached patch removes extra timestamps from the build system. Once applied, python-glance-store can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds diff -urNp python-glance-store-0.4.0.old/debian/rules python-glance-store-0.4.0/debian/rules --- python-glance-store-0.4.0.old/debian/rules 2015-04-28 10:41:45.0 -0300 +++ python-glance-store-0.4.0/debian/rules 2015-06-11 22:10:19.820794747 -0300 @@ -1,5 +1,9 @@ #!/usr/bin/make -f +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)" + PYTHONS:=$(shell pyversions -vr) PYTHON3S:=$(shell py3versions -vr) @@ -40,7 +44,7 @@ override_dh_clean: rm -rf build .testrepository override_dh_sphinxdoc: - sphinx-build -b html doc/source debian/python-glance-store-doc/usr/share/doc/python-glance-store-doc/html + sphinx-build $(SPHINXOPTS) -b html doc/source debian/python-glance-store-doc/usr/share/doc/python-glance-store-doc/html dh_sphinxdoc -O--buildsystem=python_distutils # Commands not to run ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#788503: python-osprofiler: [PATCH] please make the build reproducible
Package: python-osprofiler Version: 0.3.0-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 python-osprofiler could not be built reproducibly. The attached patch removes extra timestamps from the build system. Once applied, python-osprofiler can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds diff -urNp python-osprofiler-0.3.0.old/debian/rules python-osprofiler-0.3.0/debian/rules --- python-osprofiler-0.3.0.old/debian/rules 2014-09-04 23:16:33.0 -0300 +++ python-osprofiler-0.3.0/debian/rules 2015-06-11 22:14:36.801069933 -0300 @@ -1,5 +1,9 @@ #!/usr/bin/make -f +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)" + PYTHONS:=$(shell pyversions -vr) PYTHON3S:=$(shell py3versions -vr) @@ -45,7 +49,7 @@ override_dh_clean: rm -rf build override_dh_sphinxdoc: - sphinx-build -b html doc/source debian/python-osprofiler-doc/usr/share/doc/python-osprofiler-doc/html + sphinx-build $(SPHINXOPTS) -b html doc/source debian/python-osprofiler-doc/usr/share/doc/python-osprofiler-doc/html dh_sphinxdoc -O--buildsystem=python_distutils # Commands not to run ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#788504: python-psutil: [PATCH] please make the build reproducible
Package: python-psutil Version: 2.1.1-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 python-psutil could not be built reproducibly. The attached patch removes extra timestamps from the build system. Once applied, python-psutil can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds diff -urNp python-psutil-2.1.1.old/debian/rules python-psutil-2.1.1/debian/rules --- python-psutil-2.1.1.old/debian/rules 2014-05-02 15:57:54.0 -0300 +++ python-psutil-2.1.1/debian/rules 2015-06-11 22:19:08.349355883 -0300 @@ -1,5 +1,9 @@ #!/usr/bin/make -f +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)\" + PY2VERS := $(shell pyversions -s) PY3VERS := $(shell py3versions -s) @@ -15,7 +19,7 @@ override_dh_auto_build: for python in $(PY2VERS) $(PY3VERS); do \ $$python setup.py build; \ done - $(MAKE) -C docs html + $(MAKE) -C docs html SPHINXOPTS="$(SPHINXOPTS)" override_dh_auto_install: set -e ; \ ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#788505: python-pypump: [PATCH] please make the build reproducible
Package: python-pypump Version: 0.6-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 python-pypump could not be built reproducibly. The attached patch removes extra timestamps from the build system. Once applied, python-pypump can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds diff -urNp python-pypump-0.6.old/debian/rules python-pypump-0.6/debian/rules --- python-pypump-0.6.old/debian/rules 2015-05-13 14:48:10.0 -0300 +++ python-pypump-0.6/debian/rules 2015-06-11 22:30:19.454056240 -0300 @@ -2,6 +2,10 @@ PYTHONS:=$(shell pyversions -vr) PYTHON3S:=$(shell py3versions -vr) +LAST_CHANGE = $(shell dpkg-parsechangelog -S Date) +BUILD_DATE = $(shell LC_ALL=C date -u "+%B %d, %Y" -d "$(LAST_CHANGE)") +SPHINXOPTS := -D today=\"$(BUILD_DATE)\" + %: dh $@ --buildsystem=python_distutils --with python2,python3,sphinxdoc @@ -12,7 +16,7 @@ override_dh_clean: override_dh_auto_build: dh_auto_build - make -C docs html + make -C docs html SPHINXOPTS="$(SPHINXOPTS)" # # This version pypump-shell needs the path $HOME/.config/ # # to exist for it to build correctly, so I'm adding it ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#788507: python-repoze.tm2: [PATCH] please make the build reproducible
Package: python-repoze.tm2 Version: 2.0-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 python-repoze.tm2 could not be built reproducibly. The attached patch removes extra timestamps from the build system. Once applied, python-repoze.tm2 can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds diff -ruNp python-repoze.tm2-2.0.old/debian/rules python-repoze.tm2-2.0/debian/rules --- python-repoze.tm2-2.0.old/debian/rules 2014-09-28 12:19:16.0 -0300 +++ python-repoze.tm2-2.0/debian/rules 2015-06-11 23:01:23.412037493 -0300 @@ -2,10 +2,13 @@ #DH_VERBOSE=1 PYBUILD_NAME=python-repoze.tm2 +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)" override_dh_sphinxdoc: ifeq (,$(findstring nodocs, $(DEB_BUILD_OPTIONS))) - sphinx-build -b html docs $(CURDIR)/debian/python-repoze.tm2-doc/usr/share/doc/python-repoze.tm2-doc/html + sphinx-build $(SPHINXOPTS) -b html docs $(CURDIR)/debian/python-repoze.tm2-doc/usr/share/doc/python-repoze.tm2-doc/html dh_sphinxdoc -O--buildsystem=pybuild endif ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] [coreboot] coreboot reproducible builds almost there
Dear coreboot and reproducible build folks, Am Donnerstag, den 11.06.2015, 21:58 +0200 schrieb Patrick Georgi: > 2015-06-11 10:25 GMT+02:00 Holger Levsen : […] > > Last, and probably least: currently the headline of the page says > > "fast, flexible and reproducible Open Source firmware_?_" which I > > felt was appropriate when only a few images with payload were > > reproducible. > > Oh, I loved it, still do! At some point we should replace the > question mark with an exclamation mark, though :-) > > > Oh, and as the page says, it's currently only updated once a month > > and on demand, so please do ping me if you merged some reproducible > > changes into master! > > Thanks, will do. Let's start immediately :-) > Since you mentioned 'once we reach 100% (without payloads)' earlier: > the issue of the remaining 7 non-reproducible board should be fixed > since today, in response to your report. I'd appreciate if you could > do another run to verify this. Patrick, thanks a lot for submitting patches to fix the remaining issues. With 4.0-9975-g1f38d79 only one board is listed [1] as not reproducible buildable and that is Google Urara [2]. -3 0020: 009a 0799 afe7 009b 1d3c 0020 bd27 ...<. .' +3 0020: 009a 0719 ae47 009b 1d3c·0020·bd27 ...G...<. .' Thanks, Paul [1] https://reproducible.debian.net/coreboot/coreboot.html [2] https://reproducible.debian.net/coreboot/dbd/google_urara.html signature.asc Description: This is a digitally signed message part ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
