Bug#964248: marked as done (base-installer: Pass "--extra-suites=unreleased" to debootstrap on ports arches)

[jhcha54008 <jhcha54008@free.fr>]

Hi,

Thank you for your answer.


Le mercredi 19 août à 19h 06mn 39s (+0200), Samuel Thibault a écrit :
> jhcha54008, le mer. 19 août 2020 19:04:30 +0200, a ecrit:
> > Le lundi 17 août à 01h 06mn 05s (+0200), Samuel Thibault a écrit :
> > > My debian-cd changes create empty files so that d-i is happy (exactly
> > > like is done for -backports).
> > 
> > I am just curious : what are the expected benefits 
> > of an 'unreleased' distribution on install cdrom ?
> 
> Err, containing the content of the unreleased distribution?
> 
> So that arch-specific packages are available, as well as patched
> packages uploaded there (yes, I know, patches should be uploaded to
> sid, but there's the maintainer latency there which hinders port
> progression when not using unreleased as a staging area to be able to
> move forward without having to wait).
> 
> Samuel




I agree that this is what the 'unreleased' distribution
on debian-ports mirrors is for.

But my question was : what about the install cdrom (and not
the debian-ports mirrors) ? What are the expected benefits of
keeping a separated 'unreleased' distribution on the cdrom ?

Currently, debian-cd (when setting UNRELEASED=1) is supposed
to pull all needed packages from both suites 'unstable' and
'unreleased', and to put everything in 'sid' on the built cdrom
image. Are there use cases where this scheme is unsuitable ?

Regards,
JH Chatenet