uploading d-i to sid

[Jochen Sprickerhof]

Hi Cyril,

* Cyril Brulebois <kibi at debian.org> [2026-06-25 10:17]:
>Holger Levsen <holger at layer-acht.org> (2026-06-25):
>> <jochensp> on #debian-reproducible just now:
>>
>> "we are down to two packages in forky that FTBFS with debrebuild:
>>  command-not-found (fix in #1104517) and debian-installer (fix in git)"
>>
>> so we are wondering whether you could upload d-i to sid now or whether
>> it would be ok if we'd do it?
>>
>> i'd be happy to upload, also to DELAYED/14 or /2 :)
>>
>> Please advise what to do.
>
>Preparing an actual release is what I've been thinking about for a while
>now, and I'd rather avoid having a random upload in the archive until
>then. If I'm reading between the lines correctly you'd like all of
>*forky* to be debrebuild-able, so that wouldn't be about having an
>updated d-i in sid only, but also in forky, and some coordination with
>many other packages would be required, and I'd rather avoid imposing
>that on the relevant maintainers if we're not actually ready to build a
>release. Seeing the recent (over)flow of security updates… I really
>don't want to be in the middle of it until I've got a plan. That would
>mean getting in touch with the images team and I'm not sure I'm able or
>willing to try and get something rolling before the upcoming (double)
>point release early July…

I see your point and while a release to forky would be awesome, I think 
it would already be great to have a new version in unstable so we can 
test it on https://reproduce.debian.net/ with all architectures. I also 
just did a test and d-i from git is still reproducible.

Cheers Jochen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/reproducible-builds/attachments/20260625/92c3ec99/attachment.sig>