Your message dated Sat, 27 Sep 2008 11:32:05 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#499203: fixed in libpam-pwdfile 0.99-3.1
has caused the Debian Bug report #499203,
regarding libpam-pwdfile completely broken on hppa
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.)


-- 
499203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499203
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libpam-pwdfile
Version: 0.99-3
Severity: grave

Sep 16 17:33:43 paer sudo: PAM unable to dlopen(/lib/security/pam_pwdfile.so)
Sep 16 17:33:43 paer sudo: PAM [dlerror: /lib/security/pam_pwdfile.so: 
undefined symbol: $$dyncall]
Sep 16 17:33:43 paer sudo: PAM adding faulty module: 
/lib/security/pam_pwdfile.so

Sep 16 17:33:46 paer sudo:   weasel : pam_authenticate: Module is unknown ; 
TTY=pts/15 ; PWD=/home/weasel ; USER=root ; COMMAND=/bin/ls

Rebuilding from source does not fix this.

This affects both etch and lenny.



--- End Message ---
--- Begin Message ---
Source: libpam-pwdfile
Source-Version: 0.99-3.1

We believe that the bug you reported is fixed in the latest version of
libpam-pwdfile, which is due to be installed in the Debian FTP archive:

libpam-pwdfile_0.99-3.1.diff.gz
  to pool/main/libp/libpam-pwdfile/libpam-pwdfile_0.99-3.1.diff.gz
libpam-pwdfile_0.99-3.1.dsc
  to pool/main/libp/libpam-pwdfile/libpam-pwdfile_0.99-3.1.dsc
libpam-pwdfile_0.99-3.1_amd64.deb
  to pool/main/libp/libpam-pwdfile/libpam-pwdfile_0.99-3.1_amd64.deb



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.
Peter Palfrader <[EMAIL PROTECTED]> (supplier of updated libpam-pwdfile 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: SHA1

Format: 1.8
Date: Thu, 25 Sep 2008 12:50:11 +0200
Source: libpam-pwdfile
Binary: libpam-pwdfile
Architecture: source amd64
Version: 0.99-3.1
Distribution: unstable
Urgency: low
Maintainer: Greg Norris <[EMAIL PROTECTED]>
Changed-By: Peter Palfrader <[EMAIL PROTECTED]>
Description: 
 libpam-pwdfile - PAM module allowing authentication via an /etc/passwd-like 
file
Closes: 499203
Changes: 
 libpam-pwdfile (0.99-3.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Link using gcc instead of ld (closes: #499203).
   * Mark the pam_sm_* functions as __attribute__((visibility("default"))) and
     build with -fvisibility=hidden.
Checksums-Sha1: 
 0cbd5148a3816a4801e1fa2d44d28062819c6744 991 libpam-pwdfile_0.99-3.1.dsc
 5e6661535589cc3da4a53d987d0f94718bd7b0ba 3899 libpam-pwdfile_0.99-3.1.diff.gz
 2fbcfe78579c215f6019d1c67f8d1cad31ccee0b 14830 
libpam-pwdfile_0.99-3.1_amd64.deb
Checksums-Sha256: 
 bc17bb6b202c2d0d642abaaa408cc6b605adec16ae4fa387e6ad0f064d4d2b6a 991 
libpam-pwdfile_0.99-3.1.dsc
 ab4118789a5f47fb7354ef7cdd9ed93e5e9f2c48231234832b8a45c4241752e3 3899 
libpam-pwdfile_0.99-3.1.diff.gz
 de5f86cbad26d4d377cc493be21fb6051f1cd3872ac1fd0c7786b79078b526fd 14830 
libpam-pwdfile_0.99-3.1_amd64.deb
Files: 
 9f5cf0179cdf041f3fe85809adf9a47a 991 admin extra libpam-pwdfile_0.99-3.1.dsc
 b86ffbb68a0e6084c077ea5cf821aa12 3899 admin extra 
libpam-pwdfile_0.99-3.1.diff.gz
 542160c45695d35f0e90928ba388fb48 14830 admin extra 
libpam-pwdfile_0.99-3.1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFI23Akz/ccs6+kS90RAhEzAKCM79FaUpHgr9oGSsfwCbA+0kt0jACgl8Op
d43ncLNVOfbDrLMrwZeKWhI=
=eWh1
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to