On Thu, Sep 9, 2021 at 5:01 PM Michael Biebl <bi...@debian.org> wrote:
> Am 09.09.21 um 16:15 schrieb Michael Biebl: > > Am 09.09.21 um 15:15 schrieb Felipe Sateler: > >> It should give us the guarantees[1]: > >> > >> > The postinst script may be called in the following ways: > >> > postinst configure most-recently-configured-version > >> > The files contained in the package will be unpacked. > >> > All package dependencies will at least be “Unpacked”. > >> > If there are no circular dependencies involved, > >> > all package dependencies will be configured > >> > >> AFAICS we don't have circular dependencies, but maybe the versioned > >> breaks/replaces + versioned depends makes dpkg think there is one? > > > > Hm, we do have systemd -> systemd-timesyncd | time-daemon and > > systemd-timesyncd -> systemd > > > > This is a circular dep afaiu. > > > > I guess the only way to break this dep cycle is to drop (or rather > demote) the Depends: systemd-timesyncd | time-daemon to a Recommends. > > To ensure that systemd-timesyncd is installed during the initial > bootstrap, we'd have to bump it's prio, similar to what we did for > libpam-systemd. Either important or standard. > > Related here: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986651 > > If we can get such a change into bullseye remains to be seen. > > Does anyone else have a different idea how to approach this? > > No, I don't have any other idea. Perhaps the installer or apt teams have any ideas? -- Saludos, Felipe Sateler
