Your message dated Wed, 04 Jan 2023 21:33:47 +0000
with message-id <e1pdbon-004v3r...@fasolo.debian.org>
and subject line Bug#460232: fixed in pam 1.5.2-6
has caused the Debian Bug report #460232,
regarding Please clarify license
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 ow...@bugs.debian.org
immediately.)


-- 
460232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460232
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pam
Version: 0.99.7.1-5

Hi!  The copyright file contains:


  ALTERNATIVELY, this product may be distributed under the terms of the
  GNU General Public License, in which case the provisions of the GNU
  GPL are required INSTEAD OF the above restrictions.  (This clause is
  necessary due to a potential conflict between the GNU GPL and the
  restrictions contained in a BSD-style copyright.)

  ...

  On Debian GNU/Linux systems, the complete text of the GNU General
  Public License can be found in `/usr/share/common-licenses/GPL'.

Which version of the GPL does this refer to?  The file in
common-licenses is now actually GPLv3, but I suspect that Linux-PAM
intended to use GPLv2 or GPLv1 here.  In any case, I think the license
of the package isn't clear.

I looked in upstream sources, but couldn't find a copy of the GPL at
all, so this problem may be due to upstream.  Still, it would be good to
fix it.

/Simon



--- End Message ---
--- Begin Message ---
Source: pam
Source-Version: 1.5.2-6
Done: Sam Hartman <hartm...@debian.org>

We believe that the bug you reported is fixed in the latest version of
pam, 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 460...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sam Hartman <hartm...@debian.org> (supplier of updated pam 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 03 Jan 2023 13:15:23 -0700
Source: pam
Architecture: source
Version: 1.5.2-6
Distribution: unstable
Urgency: medium
Maintainer: Steve Langasek <vor...@debian.org>
Changed-By: Sam Hartman <hartm...@debian.org>
Closes: 460232 1004000 1022952 1024645
Changes:
 pam (1.5.2-6) unstable; urgency=medium
 .
   * Update debian/copyright, Thanks Bastian Germann, Closes: #460232
   * When pam-auth-update is called with --root,  use
     /usr/share/pam-configs from the root not from the host system, Thanks
     Johannes Schauer Marin Rodrigues, Closes: #1022952
   * Build-depend on libcrypt-dev, Closes: #1024645
   *  Add pam-auth-udpate --disable, Closes: #1004000
   * Add autopkgtests
Checksums-Sha1:
 8965f7e5f1ef5453002d92c9b4508a18b7991052 1998 pam_1.5.2-6.dsc
 9f9578052a8467782061011c6c6197b6bee69d9e 122320 pam_1.5.2-6.debian.tar.xz
Checksums-Sha256:
 2dbff29f5fc189c95b863ffd690795a7313515619ddadc470eab8a50b7555903 1998 
pam_1.5.2-6.dsc
 97adad0df930ba5ed52b88bef6d494a1b303ca2eb5be9e347479a23e4d9254fc 122320 
pam_1.5.2-6.debian.tar.xz
Files:
 e054ae6cd6a7cfc3a194c9e7b7f5d692 1998 libs optional pam_1.5.2-6.dsc
 f62abdd59a5b1eab7d9c64cf15a68860 122320 libs optional pam_1.5.2-6.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQSj2jRwbAdKzGY/4uAsbEw8qDeGdAUCY7XlGwAKCRAsbEw8qDeG
dM4sAP9YCWE0gkQXi+WnfgrAvuN4Y5YBALqLbUyolZfWNKSycgD/Xt36rP95G7jm
Fk3Z7jmOH5u08dc+S//zP9TFaCD66Qo=
=YfXI
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to