Adjust lintian overrides for latest lintian syntax.

5 files changed, 11 insertions, 10 deletions

diff --git a/debian/changelog b/debian/changelog
index 8666f60f..66c46140 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -18,6 +18,7 @@ pam (1.5.2-1) UNRELEASED; urgency=medium
   * Drop versioning of quilt build-dependency to quiet lintian, since the
     version is satisfied by oldoldoldstable.
   * Drop unused build-build-dependency on bzip2.
+  * Adjust lintian overrides for latest lintian syntax.
 
  -- Steve Langasek <vorlon@debian.org>  Wed, 17 Aug 2022 05:10:03 +0000
 
diff --git a/debian/libpam-modules-bin.lintian-overrides b/debian/libpam-modules-bin.lintian-overrides
index a40efeaf..8c185917 100644
--- a/debian/libpam-modules-bin.lintian-overrides
+++ b/debian/libpam-modules-bin.lintian-overrides
@@ -1,2 +1,2 @@
 # yes, we know it's sgid, that's the whole point...
-libpam-modules-bin: setgid-binary sbin/unix_chkpwd 2755 root/shadow
+libpam-modules-bin: setgid-binary *sbin/unix_chkpwd* 2755 root/shadow
diff --git a/debian/libpam-modules.lintian-overrides b/debian/libpam-modules.lintian-overrides
index 3eba0f93..1ae5392a 100644
--- a/debian/libpam-modules.lintian-overrides
+++ b/debian/libpam-modules.lintian-overrides
@@ -2,12 +2,12 @@
 # fortifying.  Since we know we have hardening turned on globally, suppress
 # them.  If we ever see this warning again for *other* modules, then we know
 # there's a real problem.
-libpam-modules: hardening-no-fortify-functions lib/*/security/pam_echo.so
-libpam-modules: hardening-no-fortify-functions lib/*/security/pam_filter.so
-libpam-modules: hardening-no-fortify-functions lib/*/security/pam_group.so
-libpam-modules: hardening-no-fortify-functions lib/*/security/pam_localuser.so
-libpam-modules: hardening-no-fortify-functions lib/*/security/pam_shells.so
-libpam-modules: hardening-no-fortify-functions lib/*/security/pam_wheel.so
+libpam-modules: hardening-no-fortify-functions *lib/*/security/pam_echo.so*
+libpam-modules: hardening-no-fortify-functions *lib/*/security/pam_filter.so*
+libpam-modules: hardening-no-fortify-functions *lib/*/security/pam_group.so*
+libpam-modules: hardening-no-fortify-functions *lib/*/security/pam_localuser.so*
+libpam-modules: hardening-no-fortify-functions *lib/*/security/pam_shells.so*
+libpam-modules: hardening-no-fortify-functions *lib/*/security/pam_wheel.so*
 # pam_deny.so does not use any symbol from libc.
-libpam-modules: shared-lib-without-dependency-information lib/*/security/pam_deny.so
+libpam-modules: shared-lib-without-dependency-information *lib/*/security/pam_deny.so*
 
diff --git a/debian/libpam-runtime.lintian-overrides b/debian/libpam-runtime.lintian-overrides
index 7a8b1a70..ca7d377e 100644
--- a/debian/libpam-runtime.lintian-overrides
+++ b/debian/libpam-runtime.lintian-overrides
@@ -2,4 +2,4 @@
 libpam-runtime: no-debconf-config
 # this warning is just plain crack, there's no reason that using debconf
 # outside of a maintainer script implies an error.
-libpam-runtime: debconf-is-not-a-registry usr/sbin/pam-auth-update
+libpam-runtime: debconf-is-not-a-registry *usr/sbin/pam-auth-update*
diff --git a/debian/libpam0g.lintian-overrides b/debian/libpam0g.lintian-overrides
index 5f36562d..ef3655f5 100644
--- a/debian/libpam0g.lintian-overrides
+++ b/debian/libpam0g.lintian-overrides
@@ -1,6 +1,6 @@
 # obvious multilib package false-positive; also the package name hasn't
 # changed since the glibc transition, go us!
-libpam0g: package-name-doesnt-match-sonames libpam0 libpam-misc0 libpamc0
+libpam0g: package-name-doesnt-match-sonames libpam-misc0 libpam0 libpamc0
 # yes, these are deliberately asked in the postinst because the checking
 # for daemons to be restarted needs to be done in the postinst and not 
 # before