Recoding the configuration for live-build images

[Holger Levsen]

Hi Janneke,

On Mon, Sep 06, 2021 at 12:41:49PM +0200, Jan Nieuwenhuizen wrote:
> I'm thinking about the binary seed that's used to produce a new release,
> as far as I understand it, Debian's binary seed is "build-essential".
> 
> I imagine that for a new Debian binary release, e.g., Bullseye, first
> all Bulleye's build-essential packages are built using binaries from
> Buster.

that's sadly not true.

https://en.wikipedia.org/wiki/Debian#Development is surprisingly accurate,
as is the "Flowchart of the life cycle of a Debian package" on the right.

In short: a package is once uploaded to unstable, then it's build, then
it migrates to testing, which eventually becomes stable. If there's no
new upload that package stays in unstable and (the new) testing and stable
"forever".

A package is never rebuild in Debian without a new upload.

An existing Debian port/architecture is never bootstrapped again.

(Sad. And been like this since decades so not that easy to change.)

> The idea would be to reduce the binary seed needed to build
> "build-essential".  Does that make sense?

Sadly on very differently in Debian...


-- 
cheers,
	Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

"I know what you're thinking" used to be an idiom but now it's a business model.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.reproducible-builds.org/pipermail/rb-general/attachments/20210906/65885c74/attachment.sig>