[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: debootstrap







Sent with Proton Mail secure email.

On Sunday, August 4th, 2024 at 8:06 AM, Roland Clobus <rclobus@rclobus.nl> wrote:

> Hello Maria,
> 
> On 02/08/2024 19:32, maria.shrivinski wrote:
> 
> > does somebody know how to change the (base) packages that are installed
> > during the deboostrap stage? I couldn't find anything in
> > `/usr/lib/live/build`
> > 
> > I would like to build with |lb config --distribution bookworm| but have
> > the default packages that are installed during the debootstrap stage be
> > installed from the sid (unstable) repository.
> > 
> > Is that even possible?
> 
> 
> I'm wondering why you would need to mix bookworm and sid in the
> bootstrap phase.
> That is rather early and I would not recommend to create a mixed system
> at this moment, but only later during the chroot phase, where you have
> more control over which version you will get.
> 
> Earlier this week you wrote about APT Pinning [1], is this question
> related to that?
> 
> Could you add a hooks script that does something similar to 'apt-get
> install mpv -t unstable' while the pinning for all packages from sid
> (including mpv and its dependencies) is such that it will not
> automatically happen? (You can have the mpv version from bookworm
> installed already, then it updates only a few packages)
> 
> With kind regards,
> Roland Clobus
> 
> [1] https://lists.debian.org/debian-live/2024/07/msg00023.html

Hey Roland, thanks for the reply!

Yes exactly, I wanted to have the base packages which are installed during the debootstrap stage to be pulled from sid, because I was getting dependency errors while using APT Pinning for specific sid packages.

The reason why this happened, with regards to mpv, is because the target release (bookworm) packages installed by debootstrap included certain libs with version numbers too low for the unstable release of mpv.

I tried to solve the dep errors by having the base packages pulled from sid instead. One can actually achieve this by using `lb config --distribution bookworm --distribution-chroot sid`
This will indeed install the base packages from unstable, while retaining a bookworm target release and allowing the successful installation of mpv + deps with APT Pinning and nothing else. However, if you plan on installing other bookworm packages, chances are that once again there'll be dependency errors because of the bootstrap base packages being from sid. (Same thing in reverse)

The only viable solution ended up being a chroot hook that specifically installs with `apt-get install -t unstable`, as you mentioned.

This will automatically upgrade all the dependencies of mpv from bookworm to sid.

APT Pinning does not automatically upgrade packages if newer versions are available during a live build, because of the APT:Preferences commands given in config/common.

That's why it will keep target release packages and simply return an error if a package from another release has a higher priority and higher version.

Kind Regards!


Reply to: