[Reproducible-builds] Bug#765298: marked as done (strip-nondeterminism: infinite loop when stripping certain jar files)
Your message dated Mon, 6 Jul 2015 14:07:50 +0200 with message-id 201507061407.58083.hol...@layer-acht.org and subject line closing has caused the Debian Bug report #765298, regarding strip-nondeterminism: infinite loop when stripping certain jar files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 765298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: strip-nondeterminism Version: 0.003-1 Severity: normal Line 59 of handlers/zip.pm triggers an infinite loop in Archive::Zip, but only with certain jar files. I need to create a minimal test case and file a bug report with Archive::Zip. ---End Message--- ---BeginMessage--- Hi, from #-reproducible: h01ger wonders if #765298 should be closed now - AGWA ? h01ger | its pending since february and i cannot recall having seen it recently.. mapreri the bug says it got work arounded in stri-nondeterminsm and the upstream bug in Archive::Zip is closed too. mapreri and the fix got in debian too h01ger | mapreri: will close it, quoting your+my words.. mapreri ack cheers, Holger signature.asc Description: This is a digitally signed message part. ---End Message--- ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#791574: strip-nondeterminism: failure in zip.pm, breaking package builds
package: strip-nondeterminism version: 0.008-1 severity: serious affects: golang User: reproducible-builds@lists.alioth.debian.org Usertags: toolchain Hi, from https://reproducible.debian.net/rbuild/unstable/amd64/golang_1.4.2-3.rbuild.log make[1]: Leaving directory '/tmp/buildd/golang-1.4.2' dh_installdocs -O--parallel dh_installchangelogs -O--parallel dh_installman -O--parallel dh_installdebconf -O--parallel dh_lintian -O--parallel dh_perl -O--parallel dh_link -O--parallel dh_strip_nondeterminism -O--parallel Can't call method memberNames on an undefined value at /usr/share/perl5/File/StripNondeterminism/handlers/zip.pm line 123. debian/rules:21: recipe for target 'binary' failed make: *** [binary] Error 255 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 E: Failed autobuilding of package 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] Bug#791584: kfreebsd-source-10.1: umask setting can affect build
Package: kfreebsd-source-10.1 Version: 10.1~svn274115-6 Severity: wishlist Tags: patch pending User: reproducible-builds@lists.alioth.debian.org Usertags: timestamps Hi, The kfreebsd-10 (kernel) packaging distributes a source tarball in kfreebsd-source, a binary arch-indep package. Files and directories in the tarball are owned by root:src, but permissions depend on the package builder's umask setting. To ensure reproducibility, I guess we could chmod before building the tarball: --- debian/rules(revision 5716) +++ debian/rules(working copy) @@ -170,6 +170,7 @@ mkdir -p $(SOURCE_PACKAGE)/usr/src chown -R root.src $(SRC_DIR) + chmod -R go+r-w $(SRC_DIR) # Clamp timestamps to be no newer than last changelog entry, see # https://wiki.debian.org/ReproducibleBuilds/TimestampsInTarball find $(SRC_DIR) -newermt $(BUILD_DATE) -print0 \ -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Hello my dearest beloved ,
Hello my dearest beloved , Hope all is well with you and your family . Please I am Mrs Patricia Williams from USA. I wish to donate some funds through you for Charity and to help the poor and the needy in our society. Contact me urgently on this email address: ( mrspatrici...@gmail.com ) for more information. Thanks and remain blessed. Mrs Patricia Williams. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Processed: Re: Bug#791584: kfreebsd-source-10.1: umask setting can affect build
Processing commands for cont...@bugs.debian.org: user reproducible-builds@lists.alioth.debian.org Setting user to reproducible-builds@lists.alioth.debian.org (was reproducible-builds@lists.alioth.debian.org). usertags 791584 - timestamps Usertags were: timestamps. Usertags are now: . usertags 791584 + umask There were no usertags set. Usertags are now: umask. End of message, stopping processing here. Please contact me if you need assistance. -- 791584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#791584: kfreebsd-source-10.1: umask setting can affect build
Steven Chamberlain wrote: [...] I guess we could chmod before building the tarball: On second thoughts, that's not as efficient as using tar's --mode option so I'll use that. The example given on the Debian Wiki page is more comprehensive than my chmod anyway. --- debian/rules(revision 5717) +++ debian/rules(revision 5719) @@ -176,8 +176,11 @@ | xargs -0r touch --no-dereference --date=$(BUILD_DATE) # Create tarball with files sorted in a stable order, see # https://wiki.debian.org/ReproducibleBuilds/FileOrderInTarballs + # and normalised file permissions regardless of umask, see + # https://wiki.debian.org/ReproducibleBuilds/VaryingPermissionsInTarballs find $(SRC_DIR) -print0 | LC_ALL=C sort -z \ | tar --null --no-recursion --files-from - \ + --mode=go=rX,u+rw,a-s \ -cJf $(SOURCE_PACKAGE)/usr/src/$(SRC_TAR) touch install-indep-stamp Regards, -- Steven Chamberlain ste...@pyro.eu.org ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#791618: FTBFS: assumes linux-source creates /usr/src/linux-source-3.* and it doesn't
Source: cpqarrayd Version: 2.3-3 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, as linux-source installs linux-source 4.0, and hence debian/rules fails to find it: $(wildcard /usr/src/linux-source-3.*.tar.xz) .. -- https://sources.debian.net/src/cpqarrayd/2.3-3/debian/rules/#L19 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/cpqarrayd.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] Proposal 185 - Reproducible builds: Hacking Session (Holger Levsen)
Hi Maxy, On Freitag, 19. Juni 2015, Maximiliano Curia wrote: In DebConf15, the largest BoF room will have space for a maximum of 45 people (and will have video coverage) and there will be a number of other smaller rooms with space for 15 to 20 people, without video coverage. We have quite a number of BoF proposals, and only a few of them will fit in the larger BoF room, which is of course a hard decision to take, as not all of the currently submitted BoFs will get video coverage. Taking this into account, it seems your proposal would be appropriate for in-person only. Would this be ok with you? yes, I think this is fine. Thanks 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
Re: [Reproducible-builds] Bug#790899: epydoc: please support timestamps from environment
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. 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
Re: [Reproducible-builds] checking that build succeeds in funny paths like .../1:2.3+4~5-6/...
Hi Andreas, (adding debian-qa@l.d.o to cc: and keeping full quote for the benefit of those reading this via that list...) On Sonntag, 21. Juni 2015, Andreas Beckmann wrote: (please keep me Cc:ed, I'm not subscribed) Hi, while your are doing rebuilds to check reproducibility, maybe you could also check that the packages build in a path that contains all chars that are allowed in version numbers. IIRC I had seen failures to do so twice quite recently, one was beignet, the other I forgot. You usually run into such problems when doing backports or stable updates since the version number suddenly gains '+' and/or '~'. And then you need to work around this for backports/stable As I understand you don't test reproducability with changing the build directory (seems to be embedded in too many places), so this change would need to be done for both rebuilds. Putting something like this in an A hook script (after reproduciblebuilds_user) seems to work fine with pbuilder: mkdir -p /tmp/build mv /tmp/buildd /tmp/build/pkg-1:2.3+4~5-6 ln -s build/pkg-1:2.3+4~5-6 /tmp/buildd it does not break pbuilder's assumption to build in /tmp/buildd, but all attempts to get the absolute buildroot path will contain 1:2.3+4~5-6 while I do think this is a worthwhile QA test, I don't think we should test this on the reproducible.debian.net infrastructure, for two reasons: a.) I dont think we should hunt each and every bug type, just because we have a tool to make many bugs visible - because these other bugs distract from our primary mission, which is reproducible builds. b.) in the future we will want to do rebuilds in the same pathes as done on the buildds and I doubt they will use such funny pathes. Also Debian QA already has a tool to do such tests: archive wide rebuilds as documented in https://wiki.debian.org/qa.debian.org/ArchiveTesting - so I think that's the right tool for this job. 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
