Bug#975077: libc6: circular dependencies
Package: libc6
Version: 2.31-4
Severity: important
Hello GNU libc maintainers,
There is a circular dependency between libc6, debconf, dpkg, libacl1,
libbz2-1.0, libcom-err2, libcrypt1, libgcc-s1, libgssapi-krb5-2,
libk5crypto3, libkeyutils1, libkrb5-3, libkrb5support0, liblzma5,
libnsl2, libnss-nis, libnss-nisplus, libpcre2-8-0, libselinux1,
libssl1.1, libtirpc3, perl-base, tar and zlib1g:
libc6 :Depends: libgcc-s1, libcrypt1, libnss-nis, libnss-nisplus
debconf :Pre-Depends: perl-base (>= 5.20.1-3~)
dpkg :Depends: tar (>= 1.28-1)
dpkg :Pre-Depends: libbz2-1.0, libc6 (>= 2.15), liblzma5 (>= 5.2.2), libselinux1 (>= 2.3), zlib1g (>= 1:1.1.4)
libacl1 :Depends: libc6 (>= 2.14)
libbz2-1.0 :Depends: libc6 (>= 2.4)
libcom-err2 :Depends: libc6 (>= 2.17)
libcrypt1 :Depends: libc6 (>= 2.25)
libgcc-s1 :Depends: libc6 (>= 2.14)
libgssapi-krb5-2 :Depends: libc6 (>= 2.27), libcom-err2 (>= 1.43.9), libk5crypto3 (>= 1.16), libkrb5-3 (= 1.17-10), libkrb5support0 (>= 1.15~beta1)
libk5crypto3 :Depends: libc6 (>= 2.14), libkrb5support0 (>= 1.16)
libkeyutils1 :Depends: libc6 (>= 2.14)
libkrb5-3 :Depends: libc6 (>= 2.16), libcom-err2 (>= 1.43.9), libk5crypto3 (>= 1.15~beta1), libkeyutils1 (>= 1.5.9), libkrb5support0 (= 1.17-10), libssl1.1 (>= 1.1.0)
libkrb5support0 :Depends: libc6 (>= 2.14)
liblzma5 :Depends: libc6 (>= 2.17)
libnsl2 :Depends: libc6 (>= 2.14), libtirpc3 (>= 1.0.2)
libnss-nis :Depends: libc6 (>= 2.14), libnsl2 (>= 1.0)
libnss-nisplus :Depends: libc6 (>= 2.14), libnsl2 (>> 1.3.0), libnsl2 (<< 1.3.1), libtirpc3 (>= 1.0.2)
libpcre2-8-0 :Depends: libc6 (>= 2.14)
libselinux1 :Depends: libc6 (>= 2.30), libpcre2-8-0 (>= 10.22)
libssl1.1 :Depends: libc6 (>= 2.25), debconf (>= 0.5)
libtirpc3 :Depends: libc6 (>= 2.16), libgssapi-krb5-2 (>= 1.17)
perl-base :Pre-Depends: libc6 (>= 2.29), libcrypt1 (>= 1:4.1.0), dpkg (>= 1.17.17)
tar :Pre-Depends: libacl1 (>= 2.2.23), libc6 (>= 2.17), libselinux1 (>= 1.32)
zlib1g :Depends: libc6 (>= 2.14)
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: