Re: [dpkg] 08/08: document 1.18.10.0~reproducible1

Hi, On Tue, Sep 20, 2016 at 10:36:17PM +, Mattia Rizzolo wrote: > +dpkg (1.18.10.0~reproducible1) UNRELEASED; urgency=medium > + * Continue to support --buildinfo-identifier as an override for > +--buildinfo-id, as jenkins is using it atm. shall we switch and use --buildinfo-id on

Re: New armhf node (Jetson-TK1)

On Wed, Sep 07, 2016 at 02:03:43PM -0700, Vagrant Cascadian wrote: > New armhf board up and ready for configuration. [...] > Once it's fully configured and ready for builds, please reallocate > opi2a's jobs to jtk1a done. & sorry for the delay. jtk1a is building it's first packages now \o/

Re: [PATCH] New reproducible website location

On Mon, Sep 19, 2016 at 10:09:08AM +0100, Chris Lamb wrote: > Apologies, I had assumed it was just a case of changing a few specific > lines in the Jenkins config file to point to new locations. no. we need a job then to build the stuff etc. see my previous reply to this thread… currently we

Re: [PATCH] New reproducible website location

On Mon, Sep 19, 2016 at 10:01:05AM +0100, Chris Lamb wrote: > Any update on the below? :) no. let's look at it together in Salzburg… -- cheers, Holger signature.asc Description: Digital signature ___ Reproducible-builds mailing list

Bug#837681: debug output (Re: diffoscope: 'ERROR guestfs can't be launched' when trying to compare to qubes ISOs)

On Thu, Sep 15, 2016 at 04:38:00PM +, HW42 wrote: > > 3.16.0-4-amd64 is the kernel (so jessie standard), and the host this is > > running on is a profitbricks VM, so running on kvm. > I assume you have this kernel only installed on the VM not the chroot. > So try installing linux-image-amd64

Bug#837681: debug output (Re: diffoscope: 'ERROR guestfs can't be launched' when trying to compare to qubes ISOs)

On Thu, Sep 15, 2016 at 02:58:00PM +, HW42 wrote: > It fails to find a kernel for the VM image it creates on the fly: ah, wow. > diffoscope-qubes-debug: > > supermin: failed to find a suitable kernel (host_cpu=x86_64). > > > > I looked for kernels in /boot and modules in /lib/modules. > >

Bug#837681: debug output (Re: diffoscope: 'ERROR guestfs can't be launched' when trying to compare to qubes ISOs)

Hi, these qubes ISO image files are (temporarily) now also available for download at https://jenkins.debian.net/userContent/qubes/ -- cheers, Holger signature.asc Description: Digital signature ___ Reproducible-builds mailing list

Bug#837681: debug output (Re: diffoscope: 'ERROR guestfs can't be launched' when trying to compare to qubes ISOs)

On Tue, Sep 13, 2016 at 03:35:58PM +0200, Holger Levsen wrote: > so I build an Qubes ISO, twice and ran diffoscope against it: just now I enabled debugging like this: > To see full error messages you may need to enable debugging. > Do: > export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1

Re: buildinfo of old packages

On Tue, Sep 13, 2016 at 08:14:32AM +0200, Linus Gasser wrote: > we’re doing a project where we need to build old package-versions. care to explain more? > We found the buildinfo-files on tests.reproducible-builds.org, but only for > the most recent version of the packages. Is there a way to get

Bug#837681: diffoscope: 'ERROR guestfs can't be launched' when trying to compare to qubes ISOs

On Tue, Sep 13, 2016 at 02:08:00PM +, HW42 wrote: > Since guestfs works by running a modified kernel in an VM to parse the > file system, I think it fails to start the VM (nested virt disabled, > OOM, ...). > > So I think you should first try if guestfs works at all (without > diffoscope)

Bug#837681: diffoscope: 'ERROR guestfs can't be launched' when trying to compare to qubes ISOs

On Tue, Sep 13, 2016 at 04:22:29PM +, Mattia Rizzolo wrote: > I wanted to quickly try myself, but you already deleted the files. > Could you please save them somewhere (I suppose they are too big to be > attached to the bug?) they are in /home/holger/q(1|2) on pb3, please help yourself! :-)

Bug#837681: diffoscope: 'ERROR guestfs can't be launched' when trying to compare to qubes ISOs

Package: diffoscope Version: 60 Severity: normal Hi, so I build an Qubes ISO, twice and ran diffoscope against it: holger@profitbricks-build3-amd64:~$ sudo schroot --directory /tmp -c source:jenkins-reproducible-unstable-diffoscope diffoscope -- --html /tmp/q.html --text /tmp/q.txt /tmp/q1

Re: Draft of blog post for week 72 in blog.git

On Mon, Sep 12, 2016 at 04:39:17PM +0100, Chris Lamb wrote: > > you published on Monday, I dont think there is any need to apologize for > > it. I believe publishing on Monday or Tuesday is totally fine > Regular is rationally and irrationally good for both reader and writer :) if "regular" is

Re: Draft of blog post for week 72 in blog.git

On Mon, Sep 12, 2016 at 08:52:09AM +0100, Chris Lamb wrote: > Well, I would never publish without any review - just would prefer to > have given more! :) me too, indeed. > I regrettably ended up delaying further and have just published. Apologies > this wasn't live until now. you published on

Re: Draft of blog post for week 72 in blog.git

Hi Chris, On Sun, Sep 11, 2016 at 08:33:40PM +0100, Chris Lamb wrote: > Apologies for the delay but I mismanaged my time this morning so have > only just managed to push the draft for week 72s report to blog.git. > I plan to publish it: > - http://time.is/compare/2345_11_Sept_2016_in_London

Re: [PATCH] New reproducible website location

On Fri, Sep 09, 2016 at 12:07:12PM +0100, Chris Lamb wrote: > I don't know enough about how to poke our Jenkins from Git alas. Did you not > set up many before for diffoscope, etc.? ah, it needs a jenkins job to build the website first then… and then we need to trigger this job… -- cheers,

Re: [Reproducible-builds] [PATCH] New reproducible website location

Hi Chris, sorry for the delay on this one…! On Tue, Aug 23, 2016 at 02:42:24PM +0100, Chris Lamb wrote: > We will also need to make post-update. Here is the current one: > > https://gist.github.com/lamby/0dcd68abe113ef58de0b2bfe9f4af022/raw > > Obviously, this won't work on alioth; we need

Re: New armhf node (Jetson-TK1)

On Wed, Sep 07, 2016 at 02:03:43PM -0700, Vagrant Cascadian wrote: > New armhf board up and ready for configuration. > > Thanks to Nvidia for the donation, and to Martin Michlmayr and Eric > Brower for making the arrangements! yay, very cool! thanks indeed to Nvidia, Eric & Martin! (And you,

Bug#836784: diffoscope: Several "Too much input for diff" on debian packages from unstable/amd64

Hi Ximin, On Mon, Sep 05, 2016 at 05:32:00PM +, Ximin Luo wrote: > Hi Emanuel, try setting the --max-diff-input-lines flag to a higher value. In > the next version we'll let "0" mean "unlimited" as well as having a --no-max > value to disable all such limits. Emmanuel is experiencing this

Re: [Reproducible-builds] Minimising work needed for this build-path issue

On Mon, Sep 05, 2016 at 11:26:00PM +, HW42 wrote: > Sorry I have currently no link handy. But the process for C is not very > complex: [great example] very nice, thanks for this writeup, HW42! -- cheers, Holger signature.asc Description: Digital signature

Re: [notes] 01/01: Tag 9 total packages with user_hostname_manually_added_requiring_further_investigation

Hi Emanuel, On Sun, Sep 04, 2016 at 09:22:28PM +0100, Chris Lamb wrote: > Just want to jump in here to say I think you're doing sterling > work here. likewise, many thanks for joining our efforts and contributing so nicely! (just please also tell your email client to not (only) send HTML mails…

Re: [Reproducible-builds] arm64 reproducible build network

On Fri, Sep 02, 2016 at 02:59:54PM -0700, Martin Michlmayr wrote: > LeMaker sent out an update a few weeks ago saying that there is some > PCIE problem they are still debugging before mass production can > start. thanks for the update, Martin! Still looking forward to use those boards! :-) --

Re: Bug#836377: build system terminal locale not inherited by build programs

control: reassign -1 dput control: severity -1 serious # failing to build on the buildds is RC by definition thanks Hi Ben, On Fri, Sep 02, 2016 at 10:40:17PM +1000, Ben Finney wrote: > The bug also appears on the normal buildd hosts. Should we remove >

Re: [Reproducible-builds] Deprecating plain dpkg-buildpackage

On Sat, Aug 27, 2016 at 07:29:13AM +, Mattia Rizzolo wrote: > > It could be argued that "We are mainly interested in the > > reproducibility issue, the FTBFS bugs are just a side effect". > > Indeed. > I'm fully open to such tests, but imho they would need to be on a > different project. >

Re: [Reproducible-builds] Please drop " " prefix from mailing list subject

On Sat, Aug 27, 2016 at 06:57:11AM +, Mattia Rizzolo wrote: > alright, I removed the prefix from the lists now. > While on it, I also added my address to the list of administrators. Thanks, Mattia! -- cheers, Holger signature.asc Description: Digital signature

Re: [Reproducible-builds] Please drop " " prefix from mailing list subject

On Fri, Aug 26, 2016 at 11:48:05AM +0100, Chris Lamb wrote: > I could get no further than *that* page; ie. I don't know the password… do you want to know it? -- cheers, Holger signature.asc Description: Digital signature ___

Re: [Reproducible-builds] [PATCH] Give details elems "cursor: pointer" to highlight they are clickable.

On Fri, Aug 26, 2016 at 09:56:20AM +0100, Chris Lamb wrote: > commit 3cb6d4fd7a8fdb480ed983b81c6abb8a9a1b883e > Give details elems "cursor: pointer" to highlight they are clickable. thanks, merged & deployed. -- cheers, Holger signature.asc Description: Digital signature

Re: [Reproducible-builds] [PATCH] reproducible Debian: Drop trailing underlined whitespace after package set link.

On Fri, Aug 26, 2016 at 10:01:31AM +0100, Chris Lamb wrote: > commit ae8c4d471c6fe6629c8c5cf17b60307caeda8516 > reproducible Debian: Drop trailing underlined whitespace after package > set link. thanks, merged! -- cheers, Holger signature.asc Description: Digital signature

Re: [Reproducible-builds] [PATCH] New reproducible website location

On Fri, Aug 26, 2016 at 11:24:11AM +0100, Chris Lamb wrote: > Apologies for the top-posting, but ping on the below: pong… I haven't forgotten about this, just had no time to get around to do it. Will get there :) -- cheers, Holger signature.asc Description: Digital signature

Re: [Reproducible-builds] automated diffoscope for parallel build bugs

On Fri, Aug 19, 2016 at 01:10:53PM +0100, Chris Lamb wrote: > Only from me asking: > | So, just to be 100% clear, simply varying DEB_BUILD_OPTIONS="parallel=X" > | would not have discovered this gedit bug? > Where — in context — varying meant 17 vs. 18 instead of 1 vs. 18. it wasn't clear to

Re: [Reproducible-builds] automated diffoscope for parallel build bugs

On Fri, Aug 19, 2016 at 12:32:13PM +0100, Chris Lamb wrote: > > yes, I cannot imagine there's something which is reproducible if build > > in parallel but not if not. > This entire email chain was prompted by such a case. what makes you think so? this wasn't and isn't clear for me, neither from

Re: [Reproducible-builds] automated diffoscope for parallel build bugs

Hi, On Fri, Aug 19, 2016 at 12:58:24AM +0100, Chris Lamb wrote: > > I understand that building with parallel disabled takes much longer > > for many packages so I don't know if this is just a lack of resources > It's more that we have two builds and I think (?) we would prefer to do > different

[Reproducible-builds] enable build path variation when testing unstable & experimental?

Hi, so, the question is simple: shall we enable build path variation for unstable and experimental for all tested archs now? and disable it again for testing/i386 (and the other testing archs), so that we can show how a ~90% reproducible stretch could be achieved, while we would see in unstable

Re: [Reproducible-builds] Reproducible patches for libisoburn and libisofs

On Mon, Aug 15, 2016 at 02:43:49PM +0200, Thomas Schmitt wrote: > Control via environment is unpopular on my side because it would be > a novelty in the user interface of xorriso. are you sure? I mean, usually stuff like locales and language settings are already taken from the environment…

[Reproducible-builds] Bug#834315: reference for likely causes of this bug

Hi, for future reference: please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735377#44 and followups to learn how this happened and how to prevent it. -- cheers, Holger signature.asc Description: Digital signature ___

Re: [Reproducible-builds] [Popcon-developers] Bug#833695: popularity-contest: http://popcon.debian.org/all-popcon-results.txt.gz containso

reopen 833695 severity 833695 important clone 833695 -1 reassign -1 python-popcon severity -1 normal retitle -1 python-popcon must not crash on invalid data thanks On Mon, Aug 08, 2016 at 11:34:43AM +0200, Chris Lamb wrote: > > Please reassign to python-popcon. > > Well, there are perhaps two

Re: [Reproducible-builds] Bug#833697: diffoscope: libarchive.exception.ArchiveError when running on two dmg files

On Mon, Aug 08, 2016 at 12:23:08PM +0200, Chris Lamb wrote: > This is, alas, done inconsistently. Some do it in ``recognizes` (returning > False) and some do it in ``compare_details`` but returning ``[]`` this is annoying and should be fixed. > However, most appear to not catch useful errors.

Re: [Reproducible-builds] Bug#833340: mini-buildd: please make the build reproducible

user Reproducible-builds@lists.alioth.debian.org usertag 833340 + Environment Hi, On Wed, Aug 03, 2016 at 05:20:47PM +0800, Boyuan Yang wrote: > Source: mini-buildd > Version: 1.0.16 > Severity: wishlist > Tags: patch thanks for filing this bug with patch! If you plan to file further such bugs

Re: [Reproducible-builds] [PATCH] Improve log note error messages

On Mon, Aug 01, 2016 at 05:14:09PM +0200, Chris Lamb wrote: > > Attached is the following: > Updated patch attached - I accidentally a verb. Thanks mattia! merged and deployed, thanks! -- cheers, Holger signature.asc Description: Digital signature

[Reproducible-builds] Bug#832962: Bug#832962: reprotest fails to build properly on jessie

On Sat, Jul 30, 2016 at 02:15:58AM -0400, Holger Levsen wrote: > reprotest 0.2 fails to build properly on jessie, that is, it builds but > the .deb only contains the changelog.gz and copyright. changing the line X-Python3-Version: >= 3.5 in debian/control into X-Python3-Versio

Re: [Reproducible-builds] Remaining reprotest variations

On Wed, Jul 27, 2016 at 04:58:28PM -0400, Ceridwen wrote: > > Using "setarch uname26" on non-x86 architectures may cause issues > > with recent versions of glibc, too: > All the variations can be disabled at the command line or with a config > file, so anyone using reprotest can disable `kernel`

[Reproducible-builds] Bug#832962: reprotest fails to build properly on jessie

Package: reprotest Version: 0.2 Severity: normal Hi, reprotest 0.2 fails to build properly on jessie, that is, it builds but the .deb only contains the changelog.gz and copyright. On sid it builds fine. I suppose some build depends must be adjusted, eg some versioned depends increased and some

[Reproducible-builds] Bug#832961: reprotest: please add support for building simultaneously

Package: reprotest Severity: wishlist Hi Ceridwen, while reading the very interesting thread about variations for reprotest (=congrats, nice work!), it occurred to me that it would be nice if reprotest could do both tests simultaneously, either - on two different hosts -b1node foo -b1port 4222

Re: [Reproducible-builds] Bug#787980: status: normalize file permissions when creating control.tar ?

Hi Guillem, (sorry for the late reply…) On Thu, Jul 07, 2016 at 12:20:44AM +0200, Guillem Jover wrote: > > could you please comment briefly on > > your take on this bug and it's status? > > I've had my qualms about the need for this patch, but in any > case the provided patch has not been

Re: [Reproducible-builds] [PATCH] Abstract log functions

On Wed, Jul 13, 2016 at 09:35:12AM +0200, Chris Lamb wrote: > commit 6997ba002f9bf867d542b58cb00456976e997080 > Author: Chris Lamb > Date: Wed Jul 13 09:34:45 2016 +0200 > > Abstract log functions great, thanks, merged & deployed. -- cheers, Holger

Re: [Reproducible-builds] [PATCH] Abstract log functions

On Wed, Jul 13, 2016 at 09:35:12AM +0200, Chris Lamb wrote: > Please merge from the "log-functions" branch of > https://github.com/lamby/jenkins.debian.net: > > commit 6997ba002f9bf867d542b58cb00456976e997080 seems you forgot to push? -- cheers, Holger signature.asc Description:

Re: [Reproducible-builds] [PATCH] Correct references to RBUILDLOG

Hi Chris, On Wed, Jul 13, 2016 at 08:50:22AM +0200, Chris Lamb wrote: > Please merge from the "buildlog-rbuildlog" branch of > https://github.com/lamby/jenkins.debian.net. However, not sure > this is correct (is $BUILDLOG supplied by Jenkins? Google suggests > BUILD_LOG is "it's" variable, so

Re: [Reproducible-builds] [PATCH] Rename prospects -> potential

Hi Chris, On Fri, Jul 01, 2016 at 10:55:46PM +0200, Chris Lamb wrote: > commit 047ce047a33ae136d4c3f947f0871bbe9ceee129 > potential -> prospects much better indeed, thanks! (merged+deployed) -- cheers, Holger signature.asc Description: Digital signature

[Reproducible-builds] status: normalize file permissions when creating control.tar ?

Hi, Guillem, (kudos and thanks for the recent dpkg upload(s)! Glad to see progress with reproducible bits!) could you please comment briefly on your take on this bug and it's status? It's in the BTS since 13 months without a maintainer comment. Thanks! ;-) -- cheers, Holger

Re: [Reproducible-builds] [tex-k] SORCE_DATE_EPOCH_TEX_PRIMITIVES

On Tue, Jun 14, 2016 at 02:52:39PM +0900, Norbert Preining wrote: > > no hurry. (but please do upload "soon", just not with hurry :) > Uploaded and accepted. > Please report any strangeties you might see. yay, thanks & will do! our plan is also now to build the archive with that texlive-bin

Re: [Reproducible-builds] [tex-k] SORCE_DATE_EPOCH_TEX_PRIMITIVES

On Mon, Jun 13, 2016 at 10:05:34PM +0900, Norbert Preining wrote: > Debian git is already updated, I'll upload sooner or later Are we in > hurry? no hurry. (but please do upload "soon", just not with hurry :) -- cheers, Holger signature.asc Description: Digital signature

Re: [Reproducible-builds] [tex-k] SORCE_DATE_EPOCH_TEX_PRIMITIVES

On Sun, Jun 12, 2016 at 06:19:58PM +, Karl Berry wrote: >SOURCE_DATE_EPOCH_TEX_PRIMITIVES -> FORCE_SOURCE_DATE > I changed the sources in the pdftex and tex live repositories for this. > (Thanks Norbert.) -k yay!! thanks! -- cheers, Holger (for reproducible-builds.org)

Re: [Reproducible-builds] ff2b and opi2c back online

On Sat, Jun 11, 2016 at 09:15:22PM -0700, Vagrant Cascadian wrote: > > This shall give us some more time+ease while deciding if/when to remove > > all ff2b and opi2c related jobs… > Both should be back online now! So no need to rearrange the jobs > anymore. Whew. wheeehoo indeed! Thanks for

Re: [Reproducible-builds] Question about build environments used for i386

Hi Gert, On Thu, May 26, 2016 at 01:16:03PM +0200, Gert Wollny wrote: > Sure, I've attached three screen shots of the side frame: [...] >     Proposal to reorder for simple top-down navigation  [...] >    The "I want ice cream" version:  [...] > hope that gives you an idea of what I meant. 

Re: [Reproducible-builds] [PATCH] Have index_issues also show total popcon scores of each issue

On Sat, Jun 11, 2016 at 01:11:28PM +0200, Ximin Luo wrote: > >> Oh I forgot to mention, you'll need to install python3-popcon on the > >> machine running jenkins for it to work. > Uploaded: https://packages.debian.org/jessie-backports/python-popcon cool, pushed and deployed your patch too and

Re: [Reproducible-builds] [PATCH] Reassign jobs for ff2b-armhf-rb to other nodes

On Fri, Jun 10, 2016 at 09:18:40AM -0700, Vagrant Cascadian wrote: > > thanks for the patch, before I apply something similar I have a > > question: does that mean ff2b is gone *forever*? > > Not 100% sure just yet; it still turns on, but doesn't boot. The > recovery process doesn't work, and

Re: [Reproducible-builds] [PATCH] Reassign jobs for ff2b-armhf-rb to other nodes

On Thu, Jun 09, 2016 at 01:31:39PM -0700, Vagrant Cascadian wrote: > Reassign jobs for ff2b-armhf-rb to other nodes, as it is down for the > forseeable future. thanks for the patch, before I apply something similar I have a question: does that mean ff2b is gone *forever*? if so, README and

Re: [Reproducible-builds] u-boot locale variations with it_*.UTF-8

On Thu, Jun 09, 2016 at 04:33:00AM +0200, HW42 wrote: > We found out the reason is [0] because: > GNU ld (GNU Binutils for Debian) 2.26 > GNU ld (GNU Binutils for Debian) 2.26 > ld di GNU (GNU Binutils for Debian) 2.26 wow. > While debugging this I noticed that this Makefile resets LC_ALL

Re: [Reproducible-builds] ftbfs_build-indep_not_build_on_armhf, and add bochs to it

Hi Santiago, thanks for bringing this up…! On Fri, Jun 03, 2016 at 09:13:29PM +, Santiago Vila wrote: > > +- ftbfs_build-indep_not_build_on_armhf [...] > Sometimes, packages generating "Arch: all" binary packages have good > reasons to require that those packages are built only under

[Reproducible-builds] diskspace probs on opi3c (was Re: New armhf build nodes (Odroid-U3, Cubietruck, OrangePI Plus2)

Hi, opi2c already has too little diskspace, from https://jenkins.debian.net/view/reproducible/view/Debian_setup_armhf/job/reproducible_setup_schroot_experimental_armhf_opi2c/1/console tee: /tmp/schroot-create-8VxOVXtl: No space left on device -- cheers, Holger signature.asc

Re: [Reproducible-builds] New armhf build nodes (Odroid-U3, Cubietruck, OrangePI Plus2)

Hi, the nodes are set up now, exist in jenkins and have maintenance and setup jobs configured. Next is to runs those setup jobs and then add build jobs… -- cheers, Holger signature.asc Description: Digital signature ___ Reproducible-builds

Re: [Reproducible-builds] New armhf build nodes (Odroid-U3, Cubietruck, OrangePI Plus2)

On Thu, Jun 02, 2016 at 10:59:58AM -0700, Vagrant Cascadian wrote: > Apparently had crashed and rebooted to the on-board OS. Hrmpf. Thought I > disabled that, but I'll need to disable it harder, apparently... > > Should be up now! thanks, I could login now and will now continue the setup of

Re: [Reproducible-builds] New armhf build nodes (Odroid-U3, Cubietruck, OrangePI Plus2)

Hi Vagrant, On Sun, May 29, 2016 at 09:13:20AM -0700, Vagrant Cascadian wrote: > odu3a-armhf-rb.debian.net: > cb3a-armhf-rb.debian.net: those I can reach nicely… > opi2c-armhf-rb.debian.net: > ssh port: 2245 but not this one: debug1: Connecting to opi2c-armhf-rb.debian.net [71.214.90.150]

Re: [Reproducible-builds] dropping texlive from our archive

Hi Mattia, thanks for "picking up texlive-bin"…! On Tue, May 31, 2016 at 09:52:43PM +, Mattia Rizzolo wrote: > 1+2 were already tried, with very poor results, with both upstream and > debian maintainer not interested at all at even listening to us. I think this summary is too harsh. > I

Re: [Reproducible-builds] [buildd-tools-devel] Bug#825991: sbuild: /etc/sbuild/sbuild.conf leaks the user home path

user Reproducible-builds@lists.alioth.debian.org usertag 825991 toolchain environment thanks -- cheers, Holger signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org

Re: [Reproducible-builds] arm64 reproducible build network

Hi Martin, On Wed, May 25, 2016 at 11:51:45AM -0700, Martin Michlmayr wrote: > Right. We (HPE) placed an order for some boards and they will be > shipped to ETH Zurich. It's 4 Cello boards for reproducible builds > and some more boards for other use cases (maybe ci.debian.net). looking much

Re: [Reproducible-builds] locale woes

On Sat, May 28, 2016 at 08:01:13AM -0700, Scarlett Clark wrote: > I need the locale settings for both builders please. https://tests.reproducible-builds.org/index_variations.html -- cheers, Holger signature.asc Description: Digital signature

[Reproducible-builds] kde package sets incomplete/insufficient?

Hi Scarlett, after reading http://scarlettgatelyclark.com/2016/debian-outreachy-debian-reproducible-builds-week-1-progress-report/ I checked https://tests.reproducible-builds.org/unstable/amd64/pkg_set_kde.html and

Re: [Reproducible-builds] [Tails-dev] tails binary and source packages lists URL has changed…

Hey, On Tue, May 17, 2016 at 06:48:49PM +0200, intrigeri wrote: > >> I'm working on it and hope to fix it today. > Repaired! > > I'll gladly merge this whenever you tell me I should. > Please go ahead :) cool, done.

Re: [Reproducible-builds] getting dpkg ready for reproducible sid

Hi Guillem, On Wed, May 18, 2016 at 01:58:42AM +0200, Guillem Jover wrote: > Ok, so tar 1.29 has just been released and uploaded to Debian. I've > reworked the patch as mentioned above, and will merge it for 1.18.8, > and will do the same for most of the others. awesome news! looking much

Re: [Reproducible-builds] [Tails-dev] tails binary and source packages lists URL has changed…

Hi intrigeri, On Tue, May 17, 2016 at 01:16:28PM +0200, intrigeri wrote: > The ISO build from our feature/stretch branch, that generates these > files, has been broken for a while, and after some weeks our Jenkins > set up deletes artifacts it considers to be obsolete… so these files > have

[Reproducible-builds] reproducible builds + PIE + bindnow for Stretch?(Re: Time to reevaluate the cost of -fPIC?)

On Sun, May 15, 2016 at 08:13:19PM +0200, Bálint Réczey wrote: > I think the next step could be an archive rebuild with the changed defaults I assume you are talking about a test rebuild here… first, as a next step. I'm replying here now about the "real rebuilds" coming later: reproducible

Re: [Reproducible-builds] Support for --ignore-profile flag in diffoscope

On Fri, May 13, 2016 at 12:44:11PM +0200, Ximin Luo wrote: > Concretely I have some suggestions: > > 1. instead of calling this "ignore" we call it "hide". and instead of > "irrelevant" we say "common"/"minor"/"known" strong ACK. I really really like "--hide-timestamps" much better than

Re: [Reproducible-builds] [PATCH] Have index_issues also show total popcon scores of each issue

On Wed, May 11, 2016 at 04:14:53AM +0200, Ximin Luo wrote: > Oh I forgot to mention, you'll need to install python3-popcon on the machine > running jenkins for it to work. python3-popcon is not yet available in jessie-backports, someone needs to fix this first :-) -- cheers, Holger

[Reproducible-builds] upstream fix

control: forward -1 https://developer.blender.org/rBa18f4d2bc69aa4707fb0efa92d28297d06be060e # I somewhat doubt this works but who knows… :) Hi, upstream has fixed this issue with https://developer.blender.org/rBa18f4d2bc69aa4707fb0efa92d28297d06be060e though I suppose using SOURCE_DATE_EPOCH

[Reproducible-builds] tails binary and source packages lists URL has changed…

Hi, once again these two URLs have changed: http://nightly.tails.boum.org/build_Tails_ISO_feature-stretch/lastSuccessful/archive/latest.iso.binpkgs http://nightly.tails.boum.org/build_Tails_ISO_feature-stretch/lastSuccessful/archive/latest.iso.srcpkg What are the two new URLs? :) We need to

Re: [Reproducible-builds] bpi0 armhf node disk failure

Hi Vagrant, On Mon, May 09, 2016 at 02:32:24PM -0700, Vagrant Cascadian wrote: > Reinstalled with a new SSD (which has considerably more space for > wear-levelling). > Ready for the jenkins setup scripts to be run on it! cool! installation in progress, should be back building packages rather

Re: [Reproducible-builds] getting dpkg ready for reproducible sid

On Mon, May 09, 2016 at 07:28:30PM +0200, Axel Beckert wrote: > > if (! exists($ENV{SOURCE_DATE_EPOCH_TEX_PRIMITIVES})) { > > $ENV{SOURCE_DATE_EPOCH_TEX_PRIMITIVES} = 1; > It actually has reached Debian about a month ago, but just in > Experimental: >

[Reproducible-builds] getting dpkg ready for reproducible sid

Hi, so dpkg 1.18.7 was uploaded to sid today and Mattia promply rebased our patches on it and uploaded the following changes to our repo: dpkg (1.18.7.0~reproducible0) UNRELEASED; urgency=low [ Jérémy Bobbio ] * Use a single timestamp for ar headers when building a .deb. * Use the common

[Reproducible-builds] linux-grsec: feeding the seed with SOURCE_DATE_EPOCH + usertagging

user reproducible-builds@lists.alioth.debian.org usertag 816439 randomness thanks Hi, Dato wrote: > Just FYI, the @grsecurity account tweeted the following today: > > Contrary to: https://bugs.debian.org/816439, RANDSTRUCT is > actually compatible with reproducible builds, just need to

Re: [Reproducible-builds] bpi0 armhf node disk failure

Hi, On Tue, May 03, 2016 at 11:35:07PM -0700, Vagrant Cascadian wrote: > I think bpi0's SSD may be in a very bad state. It's one of the oldest > nodes, so it's no huge surprise to see disk failures there... > > I do have an extra SSD on hand to replace it with, but it will mean a > clean

Re: [Reproducible-builds] LaTeX's \today

Hi Alexis, On Mon, May 02, 2016 at 09:18:01AM +0200, Alexis Bienvenüe wrote: > I (very awkwardly) started something at > https://www.tug.org/pipermail/tex-live/2016-May/038339.html seems you got useful feedback there and your work was generally found useful, yay! Please follow up on those

Re: [Reproducible-builds] Permission errors rendering a build unreproducible on reproducible-builds.org

Hi Sean, thanks for caring about reproducible builds and reaching out to us! On Fri, Apr 29, 2016 at 07:12:32PM -0700, Sean Whitton wrote: > My package ocrmypdf builds reproducibly on my machine. But it fails to > build at all on the reproducible-builds.org cluster. that's actually not quite

[Reproducible-builds] Bug#781262: strip-nondeterminism: remove ar handler now?

Hi, binutils 2.25-6 (which is long in testing + sid) made the build reproducible (#774429). In that course that bug was cloned into #781262, which asks for the ar handler of strip-nondeterminism to be removed. I'm slightly confused now, but (why) is binutils the only package benefitting from

Re: [Reproducible-builds] Bug#735377: 3.0 (native) silently ignores many binary files by default.

On Wed, Apr 27, 2016 at 11:15:27AM +0200, Raphael Hertzog wrote: > > DEBUILD_DPKG_BUILDPACKAGE_OPTS="-uc -us -I -i" > > Is this why? > Yes. -I and --tar-ignore in debian/source/options are cumulative. ok, thanks! I've had "-I -i" there for years & have just removed it now, curious what future

Re: [Reproducible-builds] Bug#735377: 3.0 (native) silently ignores many binary files by default.

Hi, On Tue, Apr 26, 2016 at 10:54:15AM +0200, Guillem Jover wrote: > That's weird, it does work fine here, just checked with git master to > make sure there's been no regressions: we've been seeing the same behavior when uploading diffoscope. When I build it, tests/data/test(1|2).(o|a) are not

[Reproducible-builds] usertag 821356 environment

user reproducible-builds@lists.alioth.debian.org usertag 821356 environment thanks -- cheers, Holger signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org

[Reproducible-builds] Debian Reproducible builds weekly news URL moved

Hi, you probably will have noted already but in case you haven't: Debian Reproducible Builds Weekly News has moved to a new URL: https://reproducible.alioth.debian.org/blog/ There are RSS and Atom feeds as well: https://reproducible.alioth.debian.org/blog/index.rss

Re: [Reproducible-builds] Blacklist packages for armhf

Hi Vagrant, On Sun, Apr 17, 2016 at 01:05:23PM -0700, Vagrant Cascadian wrote: > Doing some sql queires and a bit of eyeball heuristics, I've determined > the packages listed below frequently FTBFS due to timeout on armhf. cool, thanks! though… ;-) [...] … I've taken this and changed the

Re: [Reproducible-builds] LaTeX's \today

Hi Alexis, On Mon, Apr 04, 2016 at 06:24:10PM +0200, Alexis Bienvenüe wrote: > Looking at debian package canl-c, I saw it uses \today in the > documentation LaTeX files, so that it can't build reproducibly. > I also heard about gle-graphics [1], which has to be patched to give a > fixed value to

Re: [Reproducible-builds] second i386 build performed on amd64 host without using linux32

On Wed, Apr 13, 2016 at 11:45:09PM +0200, Holger Levsen wrote: > Hi Andreas, > > On Wed, Apr 13, 2016 at 03:54:14PM +0200, Andreas Beckmann wrote: > > This was only a problem in the second build, so that pbuilder seems to > > configured differently than the first

Re: [Reproducible-builds] jenkins.debian.net: [PATCH] Disable download of package descriptions

Hi Vagrant, On Sat, Apr 09, 2016 at 05:29:41PM -0700, Vagrant Cascadian wrote: > So, basically, nevermind, apparently pbuilder already does this > automatically: [...] > And looks like the builders are using 0.223~bpo8+1, and I checked the > config on one of the builders and it appears to

Re: [Reproducible-builds] Applying to Outreachy to work on Reproducible Builds

Hi Val, On Thu, Mar 24, 2016 at 10:57:03PM -0400, Valerie R Young wrote: > >(And you should have a local testbed anyway, to be able to develop+test > >your code. As its mostly about the webpages, you also dont need jenkins > >for that nor do you need to be running tests. Just experimenting with >

[Reproducible-builds] Bug#819525: diffoscope must use ruby2.3

package: diffoscope version: 51 severity: important Hi, On Tue, Mar 29, 2016 at 04:39:05AM +, Debian testing autoremoval watch wrote: > diffoscope 51 is marked for autoremoval from testing on 2016-05-04 > > It (build-)depends on packages with these RC bugs: > 818917: ruby2.2: Replaced by

Re: [Reproducible-builds] arm64 reproducible build network

Hi, On Wed, Mar 23, 2016 at 06:40:09PM -0700, Vagrant Cascadian wrote: > There's about US$1200 left. > > To follow through with number of boards in the original proposal, I > should probably get at least 3-4 more boards... or should we branch out > into an arm64 network with the remaining funds?

Re: [Reproducible-builds] Applying to Outreachy to work on Reproducible Builds

Hi Val, On Wed, Mar 23, 2016 at 03:34:33PM -0400, Valerie R Young wrote: > I'm applying to Outreachy (https://www.gnome.org/outreachy/) to work on the > Reproducible Builds project, specifically to improve > test.reproducible-builds.org. Very excited to potential join this project! welcome to

[Reproducible-builds] Bug#814057: update

control: retitle -1 "Add option to ignore mtimes" < deki> jfyi, ctimes are ignored since version 50 -- cheers, Holger signature.asc Description: Digital signature ___ Reproducible-builds mailing list

Re: [Reproducible-builds] [PATCH] Upstreaming a large amount of patches

Hi, On Wed, Mar 23, 2016 at 12:33:04AM +0100, Reiner Herrmann wrote: > > [https://lists.gnu.org/archive/html/info-gnu/2010-07/msg00023.html] > > > > " * WARNING: Future backward-incompatibility! > > " Wildcards are not documented as returning sorted values, but up to and > > " including this

Re: [Reproducible-builds] uploading .buildinfo files… (from Debian reproducible builds…)

Hi, On Fri, Mar 18, 2016 at 03:18:30PM +0100, Linus Nordberg wrote: > That's correct. Let's call it preparation for future verification of > SCT's and STH's. :D (In reality, I forgot adding info about that and > now I've decided to wait until someone asks for it.) ah, ok. > Should've rejected

Re: [Reproducible-builds] uploading .buildinfo files… (from Debian reproducible builds…)

Hi Linus, (added the Debian reproducible builds lists to cc:) On Fri, Mar 18, 2016 at 11:36:56AM +0100, Linus Nordberg wrote: > Do once (per host you're going to submit from): > > alias curl-tor='curl -A "" -x socks4a://127.0.0.1:9050/' that has an result I understand… > curl-tor -O

<    1   2   3   4   5   6   >