Dear Ivo,
> > it would seem a little antisocial to block them from migrating to
> > testing when it was "our" fault.
[…]
> I guess a lot will depends on the impact of the delay. If the difference
> in migration delay is small enough, then there would still be an
> incentive to make packages repr
hi Jathan,
fun fact: if you don't cc: me, you usually get a faster reply from me.
On Sun, Jul 21, 2019 at 08:47:46PM -0500, jathan wrote:
> Today I attended the talk "Reproducible Builds - aiming for bullseye" at
> DebConf19 and I want to share some comments since some things I consider
> we are
Hallo,
Ich hoffe, dass meine E-Mail Sie bei guter Gesundheit findet. Ich bin
William Philips. Ich möchte Ihnen etwas sehr Wichtiges mitteilen und
warte auf Ihre Antwort, damit ich Ihnen weitere Einzelheiten mitteilen
kann.
Freundliche Grüße,
William Philips
___
Hi Vagrant,
On 7/21/19 4:55 PM, Vagrant Cascadian wrote:
I think it's:
https://tests.reproducible-builds.org/reproducible-tracker.json
Which only shows results for "bullseye" (formerly only "buster).
We wanted to filter out the unstable and experimental suites from the
tracker which may h
Hi Chris,
On 7/21/19 4:09 PM, Chris Lamb wrote:
So, the devil is very much in the details here, alas. Whilst I am a
definite +1 on this idea the day-to-day experience may not be ideal
so your thoughts are very welcome.
Just to take one recent example: I noticed yesterday a regression
whereby on
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 22 Jul 2019 11:50:15 -0300
Source: strip-nondeterminism
Architecture: source
Version: 1.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Reproducible builds folks
Changed-By: Chris Lamb
Changes:
strip-n
On Mon, Jul 22, 2019 at 10:46:37AM -0300, Chris Lamb wrote:
> One question: Does your proposal also imply a source package being
> strictly reproducible in unstable or, alternatively, did you mean to
> imply it "not regressing" from being previously reproducible in
> unstable?
>
> This latter idea
strip-nondeterminism_1.3.0-1_amd64.changes uploaded successfully to localhost
along with the files:
strip-nondeterminism_1.3.0-1.dsc
strip-nondeterminism_1.3.0.orig.tar.bz2
strip-nondeterminism_1.3.0-1.debian.tar.xz
strip-nondeterminism_1.3.0-1_amd64.buildinfo
Greetings,
Your Debi
Rebecca N. Palmer wrote:
> > whereby one of our tools (strip-nondeterminism) is causing a fair
> > number of Java packages to be unreproducible — it would seem a little
> > antisocial to block them from migrating to testing when it was "our"
> > fault.
[…]
> Would it be practical to temporarily tu
Holger wrote:
> > How about if the current bonus of three days is dependent on both
> > autopkgtests *and* reproducibility? That keeps the incentive without ending
> > up with same-day migrations.
>
> /me likes!
I, too, would support this proposal.
Indeed, by keeping it as a bonus (vs. delaying
10 matches
Mail list logo
