On Wed, 2022-07-27 at 07:14 +0100, Mark Hindley wrote:
> On Mon, Jul 25, 2022 at 09:02:09PM +0200, Ansgar wrote:
> > On Mon, 25 Jul 2022 13:05:02 +0100 Mark Hindley wrote:
> > > It has been suggested that changing the dependency to
> > > 
> > >   systemd-standalone-tmpfiles | systemd-tmpfiles
> > > 
> > > would help the packaging system usually find the correct solution and 
> > > reduce the
> > > number of unexpected surprises users are reporting.
> > 
> > This change breaks debootstrap as expected:
> > 
> > +---
> > > W: Failure while installing base packages.  This will be re-attempted up 
> > > to five times.
> > > W: See /tmp/u/unstable/debootstrap/debootstrap.log for details (possibly 
> > > the package 
> > > /var/cache/apt/archives/systemd-standalone-tmpfiles_251.3-1_amd64.deb is 
> > > at fault)
> > +---
> > 
> > I hope this addresses the question for "evidence and rationale of this
> > concern" why I say this is problematic.
> 
> I assume this is the result of running debootstrap with --include
> systemd-standalone-tmpfiles?

No, I changed the dependencies of one of the involved packages to the
one suggested. But it has the same effect as an explicit --include,
i.e., it resulted in debootstrap trying to install systemd-standalone-
tmpfiles.

Ansgar

Reply via email to