Your message dated Tue, 16 Jun 2026 05:20:26 +0000
with message-id <[email protected]>
and subject line Bug#1140093: fixed in hyprlock 0.9.5-2
has caused the Debian Bug report #1140093,
regarding Update of PAM configuration necessary
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1140093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1140093
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: hyprlock
Version: 0.9.5-1
Severity: important
Control: affects -1 login
Hi,
your package currently installs a PAM configuration that includes
the "login" PAM configuration. This is a problem for multiple reasons:
1) currently there is no guarantee login is installed
2) login moved its PAM config into /usr/lib/pam.d, and PAM currently
fails to properly include files from there (1140029)
3) the Debian-correct way was to @include common-* instead.
Your pam.d file is currently:
```
# PAM configuration file for hyprlock
# the 'login' configuration file (see /etc/pam.d/login)
auth include login
```
Please replace it with:
```
@include common-auth
```
Then let me know in which version you fixed this, so login can
add Breaks: as needed.
I suggest you do this soon, as once users get the new login, your
package will fail (probably users cant unlock, if I guessed your
program's purpose correctly).
Best,
Chris
--- End Message ---
--- Begin Message ---
Source: hyprlock
Source-Version: 0.9.5-2
Done: Chow Loong Jin <[email protected]>
We believe that the bug you reported is fixed in the latest version of
hyprlock, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chow Loong Jin <[email protected]> (supplier of updated hyprlock package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 16 Jun 2026 12:22:11 +0800
Source: hyprlock
Built-For-Profiles: noudeb
Architecture: source
Version: 0.9.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Hyprland Maintainers <[email protected]>
Changed-By: Chow Loong Jin <[email protected]>
Closes: 1140042 1140093
Changes:
hyprlock (0.9.5-2) unstable; urgency=medium
.
* Patch hyprlock pam profile to use common-auth (Closes: #1140042, #1140093)
Checksums-Sha1:
6e8bed677f11873226c3d918e9444544e2f84b02 2328 hyprlock_0.9.5-2.dsc
6b449c57d7ab2a0e59d583267d474ab4243760e6 4208 hyprlock_0.9.5-2.debian.tar.xz
0b98d86f0cac0f819ba470c3ceb741255e887d72 14411
hyprlock_0.9.5-2_source.buildinfo
Checksums-Sha256:
c550cde715c67d70c093f80be89e2d7de2f3cba6c9d037c51d472b81d0aa6b38 2328
hyprlock_0.9.5-2.dsc
47c5e80b916c8e7f17022c9f5d445a1819efbf5e24fe4fdfbfa5a324a7a31ead 4208
hyprlock_0.9.5-2.debian.tar.xz
6d10a09fb6cdf3e7cf15a1d19aa07aa75e815431d8d4c6e31a1da3980106fcd2 14411
hyprlock_0.9.5-2_source.buildinfo
Files:
f8e163a7ed69e18c09b9aee4cde95355 2328 x11 optional hyprlock_0.9.5-2.dsc
f4e89ca7879ad96118c04e87c71298c6 4208 x11 optional
hyprlock_0.9.5-2.debian.tar.xz
34bb44425aa87b2104b2649a90ff7689 14411 x11 optional
hyprlock_0.9.5-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEEuDQnfs/9/dZ027Q+9UiW1iHUqEFAmow10UACgkQ+9UiW1iH
UqEoaBAAmM2z8WQdpe4bkcXBMj6iP9igumktN7WJrWvf65Toy1uNgK+z3D5p4nlI
AbLdy1BYAFjiGWiKrw9PlrLpsbn92qVxv3dUCk0yXCWZsJsHNfnseXBkEjeJVg2a
DxuUNhp4V+O/nZy4m1+ea2vFPCjfKNFtYsErjGWKi8NVxd4DR1M0iiyaGt0pMzZP
RqlmzKiJoRrejKIHHCmAvoiSyjKOX71/hs5i/ZcHT1mtxwTYM86PBkMiyMFUsL/y
FNPh9GCjrGWDa8oIhDllpqTX286xa/+Pe099Y7nupZkwXSN35J8hcPbaBVp7gEro
HbQLAGLUH8hwrPDsdgZ7yq5rDL33xw1YaIo0x09g5PZmLPz7dZHZTM436l3Cg/HY
d1kzEULunbOujF1L+HNbisAsguTP0j8DahlbhtRqpRr9Gh2WuTuglqyZUj357QG0
eOPP72hsQIiFP1Yii0uJPy0iA3qVz75/GPrv84TkL4hTakxttFG8M1NxBAQY0n2Y
GQGDYi5FyzWow/L2aw9WyB9Wtov1GViVGhswzEj7YLCvq2UTJm166PewBb0IbsqX
hkfFs5G3K0CPRL6xB9vJYROKo6BP1kgDvWwwVS32WvPINcL33Hz63gewmT9EbTM3
/oHq4aDK5ORfL8vuKXi10JA9GH7hj9zJCp9vxFzlCN3OoVsjrHQ=
=TJAo
-----END PGP SIGNATURE-----
pgp3b2WIr6nV8.pgp
Description: PGP signature
--- End Message ---
