Package: libpam-dev
Version: 1.7.0-6
Severity: important
Justification: introduces a dependency loop
Tags: patch
User: [email protected]
Usertags: rebootstrap

libpam-dev gained an unconditional dependency on libaudit-dev. This
introduces a loop:

 * libpam-dev depends on libaudit-dev
 * libaudit-dev is built from audit
 * audit build-depends on libkrb5-dev
 * libkrb5-dev is built from krb5
 * krb5 build-depends on libverto-dev
 * libverto-dev is built from libverto
 * libverto build-depends on libgio-2.0-dev
 * libgio-2.0-dev is built from glib2.0
 * glib2.0 build-depends on libmount-dev
 * libmount-dev is built from util-linux
 * util-linux build-depends on libpam-dev

This loop breaks any attempt to bootstrap unstable from source.

The pam package has a stage1 build profile that disables libaudit in
Build-Depends. When disabled, its .pc file does not mention libaudit.
Please annotate the newly introduced dependency with the same profile.

Helmut
diff -Nru pam-1.7.0/debian/changelog pam-1.7.0/debian/changelog
--- pam-1.7.0/debian/changelog  2026-06-16 05:03:10.000000000 +0200
+++ pam-1.7.0/debian/changelog  2026-07-02 08:35:28.000000000 +0200
@@ -1,3 +1,10 @@
+pam (1.7.0-6.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Do not emit libaudit-dev dependency in a stage1 build. (Closes: #-1)
+
+ -- Helmut Grohne <[email protected]>  Thu, 02 Jul 2026 08:35:28 +0200
+
 pam (1.7.0-6) unstable; urgency=medium
 
   [ Gioele Barabucci ]
diff -Nru pam-1.7.0/debian/control pam-1.7.0/debian/control
--- pam-1.7.0/debian/control    2026-06-16 05:03:10.000000000 +0200
+++ pam-1.7.0/debian/control    2026-07-02 08:35:27.000000000 +0200
@@ -69,7 +69,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: ${misc:Depends}, libpam0g (= ${binary:Version}), libc6-dev|libc-dev, 
libaudit-dev [linux-any],
+Depends: ${misc:Depends}, libpam0g (= ${binary:Version}), libc6-dev|libc-dev, 
libaudit-dev [linux-any] <!stage1>,
 Provides: libpam-dev
 Recommends: libpam-doc
 Description: Development files for PAM

Reply via email to