[Reproducible-builds] Bug#804556: datanommer.models: FTBFS: StatementError: raised as a result of Query-invoked autoflush

Source: datanommer.models Version: 0.6.4-2 Severity: serious Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org Dear Maintainer, datanommer.models fails to build from source in

[Reproducible-builds] Bug#804558: tweepy: FTBFS: ImportError: No module named {unittest2, vcr}

Source: tweepy Version: 3.4.0-1 Severity: serious Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org Dear Maintainer, tweepy fails to build from source in unstable/amd64: [..]

Re: [Reproducible-builds] new armhf node (Odroid-XU4)

Hi Vagrant, thanks a lot for this new node. I've set it up and included in the machinery now, see https://jenkins.debian.net/munin/debian.net/odxu4-armhf-rb.debian.net and https://jenkins.debian.net/munin/debian.net/odxu4-armhf-rb.debian.net/jenkins_reproducible_builds.html I've "only" added

[Reproducible-builds] Bug#804557: python-jmespath: FTBFS: ImportError: No module named nose.tools

Source: python-jmespath Version: 0.4.1-1 Severity: serious Justification: fails to build from source User: reproducible-builds@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org Dear Maintainer, python-jmespath fails to build from source in

Re: [Reproducible-builds] new armhf node (Odroid-XU4)

On 2015-11-09, Holger Levsen wrote: > thanks a lot for this new node. I've set it up and included in the machinery > now That was fast... yay! > btw, how will you attach the sdd? > http://archlinuxarm.org/platforms/armv7/samsung/odroid-xu4 only speaks about > sd-cards as far as I could see.

Re: [Reproducible-builds] GCC patch reviewed. Proposed mail for gcc-patches mailing list

Santiago Vila wrote: > So, I don't think that this patch would really be "beneficial to our > project", as it will only serve to artificially "improve" the statistics. Out of interest, would you extend this argument to argue for an arbitrary build path? Regards, -- ,''`. : :' :

[Reproducible-builds] Processing of strip-nondeterminism_0.014-1_amd64.changes

strip-nondeterminism_0.014-1_amd64.changes uploaded successfully to localhost along with the files: strip-nondeterminism_0.014-1.dsc strip-nondeterminism_0.014.orig.tar.gz strip-nondeterminism_0.014-1.debian.tar.xz dh-strip-nondeterminism_0.014-1_all.deb

[Reproducible-builds] Processed: Re: dh-strip-nondeterminism: Breaks crypto signatures on Mono packages, breaking pkg installs

Processing commands for cont...@bugs.debian.org: > tags 804600 + pending Bug #804600 [dh-strip-nondeterminism] dh-strip-nondeterminism: Breaks crypto signatures on Mono packages, breaking pkg installs Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

[Reproducible-builds] Bug#804600: dh-strip-nondeterminism: Breaks crypto signatures on Mono packages, breaking pkg installs

tags 804600 + pending thanks Hi, > I now need to do fifty sourceful uploads with > "override_dh_strip_nondeterminism" stanzas added. That seems excessive. I'll just upload a fix instead.. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org /

[Reproducible-builds] Bug#804600: marked as done (dh-strip-nondeterminism: Breaks crypto signatures on Mono packages, breaking pkg installs)

Your message dated Tue, 10 Nov 2015 00:19:03 + with message-id and subject line Bug#804600: fixed in strip-nondeterminism 0.014-1 has caused the Debian Bug report #804600, regarding dh-strip-nondeterminism: Breaks crypto signatures on Mono packages,