Re: package uploaded to our repo

On Tue, Feb 14, 2017 at 04:52:22PM +1300, Chris Lamb wrote: > No. This upload to our repo adds new codepaths to Python 2.7 which are then > enabled on the "b" build on jenkins.debian.net; see > <1486933699.96290.878650304.07373...@webmail.messagingengine.com> for the > background. ic, thanks.

Re: would/Does it make sense to have .buildinfo feature into compiling tools as well ?

shirish शिरीष: > Dear all, > > My idea/suggestion may be crap but still please go through it. > > From whatever little I understand of reproducible builds, one of the > basic things it tries to do is have a .buildinfo file which can be > shared with the other person so that s(he) can use the

Re: [diffoscope] diffoscope commit mails

On Tue, Feb 07, 2017 at 07:16:41PM +0100, Mattia Rizzolo wrote: > On Tue, Feb 07, 2017 at 06:04:35PM +, Holger Levsen wrote: > > > > Shouldn't we drop the mails to > > > > reproducible-comm...@lists.alioth.debian.org > > > > and just send them to diffosc...@lists.reproducible-builds.org?! > >

would/Does it make sense to have .buildinfo feature into compiling tools as well ?

Dear all, My idea/suggestion may be crap but still please go through it. From whatever little I understand of reproducible builds, one of the basic things it tries to do is have a .buildinfo file which can be shared with the other person so that s(he) can use the .buildinfo file to generate the

Re: [diffoscope] diffoscope commit mails

On Tue, Feb 14, 2017 at 07:50:11PM +, Holger Levsen wrote: > > > hm, that makes rb-commits@l.r-b.o more noisy and less specific, so maybe > > > we should > > > use diffoscope-comm...@lists.reproducible-builds.org instead? > > > > I don't think it wold: rb-commits is *not used* at all right

Re: diffoscope 77 in stretch or not?

Holger Levsen: > On Tue, Feb 14, 2017 at 09:38:51AM +1300, Chris Lamb wrote: >>> what did you plan on to do with diffoscope in regard to Debian's >>> stretch when you decided to work on it >> I didn't decide anything at all; I was enjoying the coding, adding >> features, tests, squashing bugs... >

Bug#855169: diffoscope: use BSD-style stat on FreeBSD

Package: diffoscope Version: 77 >From GNU stat output diffoscope filters those parts that are allowed to change. The BSD stat(1) command does not match the output format and reports undesired differences: % python3 setup.py test --pytest-args="-rsx -l -vv

Re: diffoscope 77 in stretch or not?

On Tue, Feb 14, 2017 at 09:38:51AM +1300, Chris Lamb wrote: > > what did you plan on to do with diffoscope in regard to Debian's > > stretch when you decided to work on it > I didn't decide anything at all; I was enjoying the coding, adding > features, tests, squashing bugs... you decided to put

Re: [diffoscope] diffoscope commit mails

On Tue, Feb 14, 2017 at 08:59:59PM +0100, Mattia Rizzolo wrote: > > To: reproducible-comm...@lists.alioth.debian.org, > > diffosc...@lists.reproducible-builds.org > that's a different mailing list, on alioth, reproducible-commits. > I'm talking about rb-commits, on reproducible-builds.org: >

Re: diffoscope 77 in stretch or not?

On Tue, Feb 14, 2017 at 08:44:00PM +, Ximin Luo wrote: > I do think it's OK to try to support diffoscope 67 for 2 years because it's > been quite well tested. well, yes… but… > I understand that 77 fixes quite a lot of bugs over 67… 77 *exists* and is quite probably a lot better than 67,

Another new armhf node (Pine64+)

Yet Another arm board ready to be configured for the build farm! p64c-armhf-rb.debian.net: Pine64+, Allwinner A64 (cortex-a53) quad-core, 2GB ram ssh port: 2248 ssh fingerprints: 2048 7e:11:62:84:b2:e8:cd:2b:52:f5:41:c1:98:bf:7a:d2 (RSA) 256 83:48:b1:c2:11:45:5c:51:9d:67:d1:58:0a:95:3d:33 (ECDSA)

Искате да отидете на мечтаната ски ваканция?

Здравейте,Ще Ви помогнем за мечтаните покупки с бърз online заем до 2 000 лева - влезте в NaZaem.bg изберете желаните от Вас сума, срок и попълнете формата за кандидатстване. Молбата Ви ще бъде разгледана и ако е одобрена ще наредим сумата по посочената от Вас банкова сметка или каса на