Hi Andrej, On Sat, Nov 12, 2022 at 03:26:48PM +0100, Andrej Shadura wrote: > After my yesterday’s upload of pkgconf replacing pkg-config, Helmut was > fighting a dependency cycle in rebootstrap:
Just because you added th cycle does not mean libxcrypt is the best place to break it. Actually, pkgconf does not use libxcrypt, so I can just order it before libxcrypt. It doesn't "just work" automatically, but the manual ordering is not an issue otherwise. Long term, I'd like to see libc6-dev stop depending on libcrypt-dev at which point the cycle is also broken. > diff --git a/debian/control b/debian/control > index 622438845ba6..da34259abd14 100644 > --- a/debian/control > +++ b/debian/control > @@ -3,7 +3,8 @@ Section: admin > Priority: optional > Maintainer: Marco d'Itri <m...@linux.it> > Build-Depends: debhelper-compat (= 13), > - autoconf, automake, libtool, pkg-config, > + autoconf, automake, libtool, > + pkg-config <!pkg.libxcrypt.nopkgconfig>, > Standards-Version: 4.6.1.1 > Rules-Requires-Root: no > Vcs-Git: https://salsa.debian.org/md/libxcrypt.git Please don't. This is a really strange profile with difficult to understand semantics. rebootstrap won't need it. Any objections to just closing the bug with no action? Helmut
