[Reproducible-builds] Bug#792221: libnet-frame-device-perl: FTBFS without networking: t/04-new-default and t/05-new-target fail
Source: libnet-frame-device-perl Version: 1.10-1 Severity: important Tags: sid User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build without networking, including on pbuilder's default setup: Test Summary Report --- t/04-new-default.t (Wstat: 25856 Tests: 0 Failed: 0) Non-zero exit status: 101 Parse errors: Bad plan. You planned 1 tests but ran 0. t/05-new-target.t (Wstat: 25856 Tests: 0 Failed: 0) Non-zero exit status: 101 Parse errors: Bad plan. You planned 1 tests but ran 0. Files=5, Tests=3, 1 wallclock secs ( 0.04 usr 0.02 sys + 0.40 cusr 0.05 csys = 0.51 CPU) Result: FAIL Failed 2/5 test programs. 0/3 subtests failed. Makefile:861: recipe for target 'test_dynamic' failed Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/libnet-frame-device-perl.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-22-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#792224: node-oauth: FTBFS without networking: Error: getaddrinfo ENOTFOUND
Source: node-oauth Version: 0.9.11-1 Severity: important Tags: sid stretch User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build when internet connectivity is not available, such as in pbiulder: When using the SHA1 Hashing function ✓ we get the specified digest as described in http://oauth.net/core/1.0/#sig_base_example (A.5.2) ✓ OK » 67 honored (0.046s) events.js:72 throw er; // Unhandled 'error' event ^ Error: getaddrinfo ENOTFOUND at errnoException (dns.js:37:11) at Object.onanswer [as oncomplete] (dns.js:124:16) debian/rules:15: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 8 I can't see an actual failing test in the output. Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/node-oauth.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-22-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] Bug#791823: debhelper: set SOURCE_DATE_EPOCH env var for reproducible builds
Hi! Dhole: Also, in order to help reproducible builds, a fixed timezone is exported (TZ=UTC). I am not convinced this change is a good idea. While reviewing new uploads to the Debian archive, I have at least spotted these lines in exim4/4.86~RC4-1 changelog [1]: * unexport/undefine TZ in debian/rules for reproducible build. It would be used as default value for TIMEZONE_DEFAULT. The `TZ` environment variable is not usually set in a build environment. It is a reproducibility problem if a package produce different binaries when it is, but that's all. I am afraid that some packages, like exim4, would silently start behaving differently if we set `TZ` in debhelper. If we don't set the variable in debhelper, we can use the reproducibility tests to spot packages who are building differently depending on the timezone or the value of TZ and propose fixes to maintainers. This enables them to review their impact. It is indeed more work, but it's less likely to unknowingly introduce any weird behavior. [1]: https://tracker.debian.org/news/694090 -- Lunar.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: 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#792161: FTBFS: test_http etc. fail with ConnectionError: Connection aborted
Source: python-wsgi-intercept
Version: 0.8.1-2
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:
test/test_httplib2.py ...
test/test_requests.py FFF.FFF
test/test_urllib.py ..
test/test_wsgi_compliance.py .
=== FAILURES ===
__ test_http ___
def test_http():
with InstalledApp(wsgi_app.simple_app, host=HOST, port=80) as app:
resp = requests.get('http://some_hopefully_nonexistant_domain:80/')
test/test_requests.py:24:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python2.7/dist-packages/requests/api.py:69: in get
return request('get', url, params=params, **kwargs)
/usr/lib/python2.7/dist-packages/requests/api.py:50: in request
response = session.request(method=method, url=url, **kwargs)
/usr/lib/python2.7/dist-packages/requests/sessions.py:465: in request
resp = self.send(prep, **send_kwargs)
/usr/lib/python2.7/dist-packages/requests/sessions.py:573: in send
r = adapter.send(request, **kwargs)
except (ProtocolError, socket.error) as err:
raise ConnectionError(err, request=request)
E ConnectionError: ('Connection aborted.', gaierror(-2, 'Name or
service not known'))
/usr/lib/python2.7/dist-packages/requests/adapters.py:415: ConnectionError
= 6 failed, 23 passed in 0.84 seconds ==
E: pybuild pybuild:256: test: plugin distutils failed with: exit code=1: cd
/tmp/buildd/python-wsgi-intercept-0.8.1/.pybuild/pythonX.Y_2.7/build; python2.7
-m pytest
This happens on builders with public internet connectivity, and on builders
with only `lo`.
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/python-wsgi-intercept.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-22-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#792178: gunroar: please make the build reproducible
Source: gunroar Version: 0.15.dfsg1-7 Severity: wishlist Tags: patch User: reproducible-builds@lists.alioth.debian.org Usertags: locale X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org Hi! While working on the reproducible builds effort [1], we have noticed that gunroar could not be built reproducibly. The order of source files varies depending on the locale. The attached patch fixes this by setting LC_ALL to C before sorting. Regards, Reiner [1]: https://wiki.debian.org/ReproducibleBuilds diff --git a/debian/patches/makefile.patch b/debian/patches/makefile.patch index 9bc724a..86c14f9 100644 --- a/debian/patches/makefile.patch +++ b/debian/patches/makefile.patch @@ -5,7 +5,7 @@ +++ b/Makefile @@ -0,0 +1,11 @@ +GDC=gdc -+DSRC=$(shell find import src/abagames -name *.d | sort) ++DSRC=$(shell find import src/abagames -name *.d | LC_ALL=C sort) +EXE=gunroar + +all: $(EXE) 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#792193: FTBFS: t/test_filters.t fails with TAP syntax errors
Source: xmltv Version: 0.5.63-2 Severity: serious Tags: sid Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails its tests: Test Summary Report --- t/test_filters.t (Wstat: 0 Tests: 99 Failed: 1) Failed test: 49 Parse errors: Tests out of sequence. Found (51) but expected (50) Tests out of sequence. Found (52) but expected (51) Tests out of sequence. Found (53) but expected (52) Tests out of sequence. Found (54) but expected (53) Tests out of sequence. Found (55) but expected (54) Displayed the first 5 of 51 TAP syntax errors. Re-run prove with the -p option to see them all. Files=5, Tests=124, 110 wallclock secs ( 0.12 usr 0.01 sys + 78.00 cusr 8.44 csys = 86.57 CPU) Result: FAIL Failed 1/5 test programs. 1/124 subtests failed. Makefile:1930: recipe for target 'test_dynamic' failed make[1]: *** [test_dynamic] Error 255 make[1]: Leaving directory '/tmp/buildd/xmltv-0.5.63' Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/xmltv.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-22-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#792196: FTBFS: AUD/AUD lt-stacktrace (/Stacktrace/fct/normal/test_traceback) fails: FAILED_ASSERTION
Source: diagnostics Version: 0.3.3-10 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, apparently in this test. I totally don't understand which bit is the actual error, however: Started RUN with mask /* and level AUD with build Level AUD in test application /tmp/buildd/diagnostics-0.3.3/diagnostics/extensions/stacktrace/.libs/lt-stacktrace Test_Run_Result [jenkins 8204/140649083651904]: CASE=/Stacktrace/fct/normal/test_posix (build: AUD target: PRO) in 0.000270 secs SUCCEEDED Test_Run_Result [jenkins 8204/140649083651904]: CASE=/Stacktrace/fct/normal/test_posix_process (build: AUD target: PRO) in 1.012428 secs SUCCEEDED Test_Run_Result [jenkins 8204/140649083651904]: CASE=/Stacktrace/fct/normal/test_traceback (build: AUD target: PRO) in 0.225559 secs FAILED_ASSERTION [TES]: CONDITION=((v.loc.at(0).function) == (call_my_visitor_2)) EXCEPTION=::diagnostics::unittest::Test_Exception WHAT=(v.loc.at(0).function)==(call_my_visitor_2) EVALUATES TO (diagnostics::testing::COMPONENT_Stacktrace::test_traceback(diagnostics::unittest::Test_Data))==(call_my_visitor_2) [stacktrace.t.cpp stacktrace.t.cpp 214] UNEXPECTED_EXCEPTION [TES]: at the end of CASE=/Stacktrace/fct/normal/test_traceback EXCEPTION=Test_Exception WHAT=(v.loc.at(0).function)==(call_my_visitor_2) EVALUATES TO (diagnostics::testing::COMPONENT_Stacktrace::test_traceback(diagnostics::unittest::Test_Data))==(call_my_visitor_2) [ 0] FAILED: 2 failure(s) counted. Finished RUN with mask /* and level AUD with build Level AUD in test application /tmp/buildd/diagnostics-0.3.3/diagnostics/extensions/stacktrace/.libs/lt-stacktrace SUCCESS 2 ( 66%) FAILURES1 ( 33%) INVALIDATIONS 0 ( 0%) TOTAL 3 FAIL: stacktrace Exception std::out_of_range: vector::_M_range_check: __n (which is 0) = this-size() (which is 0) at /usr/lib/x86_64-linux-gnu/libstdc++.so.6@0x67645 at /usr/lib/x86_64-linux-gnu/libstdc++.so.6@0x67690 at /usr/lib/x86_64-linux-gnu/libstdc++.so.6@0x678a8 at /usr/lib/x86_64-linux-gnu/libstdc++.so.6@0x8a974 at /lib/x86_64-linux-gnu/libc.so.6@0x21b44 at /tmp/buildd/diagnostics-0.3.3/diagnostics/extensions/stacktrace/.libs/lt-use_case@0x4007a1 at unknown@0x Aborted XFAIL: use_case = 1 of 2 tests failed Please report to christ...@schallhart.net = Makefile:671: recipe for target 'check-TESTS' failed make[11]: *** [check-TESTS] Error 1 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/diagnostics.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-22-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#792158: FTBFS: FactoryLocator.java:30: error: package org.apache.geronimo.osgi.locator does not exist
Source: geronimo-stax-1.2-spec Version: 1.1-1 Severity: serious Tags: sid Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build in sid: compile: [mkdir] Created dir: /tmp/buildd/geronimo-stax-1.2-spec-1.1/build/classes [javac] /tmp/buildd/geronimo-stax-1.2-spec-1.1/debian/build.xml:31: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 37 source files to /tmp/buildd/geronimo-stax-1.2-spec-1.1/build/classes [javac] /tmp/buildd/geronimo-stax-1.2-spec-1.1/src/main/java/javax/xml/stream/FactoryLocator.java:30: error: package org.apache.geronimo.osgi.locator does not exist [javac] import org.apache.geronimo.osgi.locator.ProviderLocator; [javac]^ [javac] /tmp/buildd/geronimo-stax-1.2-spec-1.1/src/main/java/javax/xml/stream/FactoryLocator.java:86: error: cannot find symbol [javac] String factoryClassName = ProviderLocator.lookupByJREPropertyFile(lib + File.separator + stax.properties, factoryId); I guess this is incompatability with libgeronimo-osgi-support-java 1.1 (1.0 in testing works). Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/geronimo-stax-1.2-spec.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-22-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#792159: FTBFS: html2article/conv.go: ...go.net/html expects import golang.org/x/net/html
Source: golang-go.tools Version: 0.0~hg20140703-4 Severity: serious Tags: sid Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: dh_auto_build override_dh_auto_build can't load package: the code.google.com/p/go.tools/cmd/cover command has moved; use golang.org/x/tools/cmd/cover instead. can't load package: the code.google.com/p/go.tools/cmd/godoc command has moved; use golang.org/x/tools/cmd/godoc instead. can't load package: the code.google.com/p/go.tools/cmd/vet command has moved; use golang.org/x/tools/cmd/vet instead. cd obj-x86_64-linux-gnu go install -v code.google.com/p/go.tools/astutil code.google.com/p/go.tools/blog code.google.com/p/go.tools/blog/atom code.goog... src/code.google.com/p/go.tools/cmd/html2article/conv.go:21:2: code in directory /golang-go.tools-0.0~hg20140703/obj-x86_64-linux-gnu/src/code.google.com/p/go.net/html expects import golang.org/x/net/html src/code.google.com/p/go.tools/cmd/html2article/conv.go:22:2: code in directory /golang-go.tools-0.0~hg20140703/obj-x86_64-linux-gnu/src/code.google.com/p/go.net/html/atom expects import golang.org/x/net/html/atom src/code.google.com/p/go.tools/playground/socket/socket.go:38:2: code in directory /golang-go.tools-0.0~hg20140703/obj-x86_64-linux-gnu/src/code.google.com/p/go.net/websocket expects import golang.org/x/net/websocket ... Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/golang-go.tools.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-22-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#792157: flask-sqlalchemy: Not installable: Depends: python-sqlalchemy ( 0.10) but 1.0.6+ds1-1 is in sid
Package: flask-sqlalchemy Version: 1.0-2 Severity: serious Tags: sid User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package cannot be installed in sid: # apt-get install python-flask-sqlalchemy The following packages have unmet dependencies: python-flask-sqlalchemy : Depends: python-sqlalchemy ( 0.10) but 1.0.6+ds1-1 is to be installed E: Unable to correct problems, you have held broken packages. This is causing e.g. flask-migrate to FTBFS. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-22-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] [pdftex] Please make the CreationDate, ModDate and ID field deterministic
Hi, On 07/12/2015 12:02 AM, Karl Berry wrote: Meanwhile, Thanh has already made changes in the pdftex source repository, revision 724 at https://foundry.supelec.fr/scm/viewvc.php/branches/stable/source/?root=pdftex (project page: https://foundry.supelec.fr/projects/pdftex/) I append his message about it (sent privately). Will it suffice for you? --karl It suffices, but it now shifts the problem somewhere else. The SOURCE_DATE_EPOCH environment variable is an easy way for distributions like Debian, openSUSE, and Ubuntu to set that variable during all their builds and immediately get the supporting packages reproducible. If pdftex does not support that environment variable but instead only offers latex macros to make the timestamps and ID field reproducible then we now have to fix all tools that make use of pdflatex. In Debian 616 source packages directly or indirectly build-depend on pdflatex. Surely many of them can be fixed by fixing other toolchain packages like Doxygen-latex but others will have to be manually patched. We also often get a response like why do I have to patch my software?, can't that other software be changed instead?. If you decide not to integrate support for SOURCE_DATE_EPOCH then we would appreciate if you could layout your reasoning for such decision so that we can refer other package maintainers to that email. Thank you for your consideration, Cheers, akira ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#792181: tth: please make the build reproducible
Source: tth
Version: 4.05+ds-1
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org
Hi!
While working on the reproducible builds effort [1], we have noticed
that tth could not be built reproducibly.
The build timestamp is embedded into several HTML files.
The attached patch fixes this by removing the timestamp from generated
HTML files, as it provides no useful information anyway.
Regards,
Reiner
[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/patches/reproducible_build.patch b/debian/patches/reproducible_build.patch
new file mode 100644
index 000..1008736
--- /dev/null
+++ b/debian/patches/reproducible_build.patch
@@ -0,0 +1,41 @@
+Author: Reiner Herrmann rei...@reiner-h.de
+Description: Don't embed timestamp into HTML
+ For generated HTML files, the current timestamp is embedded.
+ As this prevents the package from building reproducible and
+ provides no useful information it can be removed.
+
+Index: tth-4.05+ds/tthg.lex
+===
+--- tth-4.05+ds.orig/tthg.lex
tth-4.05+ds/tthg.lex
+@@ -5977,7 +5977,6 @@ char ttver[]=TTH_VERSION;
+ char ttname[20];
+ time_t secs_elapsed;
+ time_t make_time=939087164;
+-char timestr[]=On 00 Jan 2000, 00:00.;
+ FILE *fdin=0;
+ int horizmode=1; /* In signoff use font tags not divs */
+ char main_input[TTH_CHARLEN];
+@@ -6135,20 +6134,12 @@ char main_output[TTH_CHARLEN];
+ yylex();
+ fprintf(stderr, Number of lines processed approximately %d\n,
+ tth_num_lines-1);
+- /* Time stamp */
+- time(secs_elapsed);
+- spoint=ctime(secs_elapsed);
+- strncpy(timestr+3,spoint+8,2);
+- strncpy(timestr+6,spoint+4,3);
+- strncpy(timestr+10,spoint+20,4);
+- strncpy(timestr+16,spoint+11,5);
+- if(raw==2)*timestr=0; /* Not if -r2 */
+ if(raw!=1 raw != 4){
+ fprintf(tth_fdout,\nbr /br /hr /smallFile translated from\n\
+ Tsub%sE%s/subX\nby a href=\http://hutchinson.belmont.ma.us/tth/\;\n\
+ Tsub%sT%s/sub%s/a,\n\
+-version %s.br /%s/small\n,TTH_SMALL,TTH_SIZEEND,TTH_SMALL,TTH_SIZEEND
+- ,TTH_NAME,TTH_VERSION,timestr);
++version %s./small\n,TTH_SMALL,TTH_SIZEEND,TTH_SMALL,TTH_SIZEEND
++ ,TTH_NAME,TTH_VERSION);
+ }
+ if(raw!=1){
+ if(tth_htmlstyle3)fprintf(tth_fdout,/div/body);
diff --git a/debian/patches/series b/debian/patches/series
index 8e030db..9f5fb8c 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -8,3 +8,4 @@ secure-upstream-doc.patch
silence-upstream-doc.patch
debianization.patch
debianization-clean.patch
+reproducible_build.patch
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#792197: FTBFS: SDLTimerTest.test_SDL_GetTicks fails, others flaky
Source: pysdl2 Version: 0.9.3+dfsg2-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, with some tests always failing, and some apparently failing inconsistently: -- FAILURE: test_SDL_GetTicks (sdl2.test.timer_test.SDLTimerTest) == Traceback (most recent call last): File /pysdl2-0.9.3+dfsg2/sdl2/test/timer_test.py, line 35, in test_SDL_GetTicks ticks2, ticks)) AssertionError: 1: 4.00 is not = 3 for 1004.00 and 0.00 test_SDL_Delay and test_MPEventHandler__call__ have also failed. Full build log showing all three (as of now): https://reproducible.debian.net/rb-pkg/unstable/amd64/pysdl2.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-22-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#792201: doxygen: Honour SOURCE_DATE_EPOCH environment variable for reproducible output
Source: doxygen Version: 1.8.9.1-3 Severity: wishlist Tags: upstream patch User: reproducible-builds@lists.alioth.debian.org Usertags: toolchain timestamps Control: block -1 by 791823 Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=751984 Hi, this bug is to track the progress of the upstream bug linked to above in Debian. This of course should not stop you from including the patch in Debian before upstream includes it in its next release =). Cheers, akira ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#792202: texlive-bin: Please make the CreationDate, ModDate and ID field deterministic
Source: texlive-bin Version: 2015.20150524.37493-5.1 Severity: wishlist Tags: upstream patch User: reproducible-builds@lists.alioth.debian.org Usertags: toolchain timestamps Control: block -1 by 791823 Control: forwarded -1 http://tug.org/pipermail/pdftex/2015-July/008952.html Hi, this bug is to track the progress of the upstream bug linked to above in Debian. This of course should not stop you from including the patch in Debian before upstream includes it in its next release =). Cheers, akira ___ 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#790899: epydoc: please support timestamps from environment
On Mon, Jul 6, 2015 at 1:38 PM, Kenneth Pronovici prono...@debian.org wrote: On Thu, Jul 2, 2015 at 3:27 PM, Reiner Herrmann rei...@reiner-h.de wrote: Thanks for considering it! :) We uploaded also a patched epydoc to our repository today and are currently rebuilding affected packages [1]. The page should be updated soon. Ok, what you're asking for makes sense to me. I agree that it seems worthwhile to make these changes in Epydoc. I'm traveling this week for work. Unless Edward objects, I'll plan to apply the patch and upload a new package to unstable sometime after I'm back, hopefully no later than next weekend. I have filed a related bug in the upstream bug tracker: https://sourceforge.net/p/epydoc/bugs/368/ I updated the original patch to include man/epydoc.1, adding a section called REPRODUCIBLE BUILD BEHAVIOR. I also tweaked the patch description to better match the bug report I filed at SourceForge. I'll be uploading 3.0.1+dfsg-8 later today, including this patch. I have tested epydoc's general behavior, but I have not specifically tested the behavior around SOURCE_DATE_EPOCH. I am assuming you will tell me if the current version of the package does not meet your needs for the Reproducible Builds effort. Please let me know if you need anything else. KEN -- Kenneth J. Pronovici prono...@debian.org ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
