Re: bits from the release team

On 18/05/2026 14:26, Jochen Sprickerhof wrote:
> Hi Peter,
> 
> * Peter Blackman <[email protected]> [2026-05-18 14:17]:
>>> We're about half-way the forky release cycle and we'd like to update you on a
>>> small step in code, but a giant leap in commitment.
>>>
>>> Reproducibility
>>> ===============
>>>
>>> Aided by the efforts of the Reproducible Builds project [1], we've decided it's
>>> time to say that Debian must ship reproducible packages. Since yesterday, we
>>> have enabled our migration software to block migration of new packages that
>>> can't be reproduced [2] or existing packages (in testing) that regress in
>>> reproducibility.
>>
>> do you literally mean just "new" packages,
>> (i.e. packages that are not currently in the archive),
>>
>> or does this also include packages deemed NEW because
>> they have the upstream version number in the package name
>> (shared libraries, build tools etc.)?
> 
> New as in packages not in the testing distribution.
> 
> Cheers Jochen

Hi,

This doesn’t really answer my intended question.

Suppose packagefoo7 is in the testing distribution.
That is packagefoo (upstream version 7)

packagefoo8 is then uploaded, a new upstream version of packagefoo.

What happens? (assuming both are unreproducible)


Cheers,
Peter