Your message dated Mon, 17 May 2010 07:47:06 +0000
with message-id <e1odv2y-0007ob...@ries.debian.org>
and subject line Bug#578650: fixed in pam-python 0.1.1-1
has caused the Debian Bug report #578650,
regarding ITP: libpam-python -- a PAM Module that runs the Python interpreter
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.)
--
578650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
* Package name : libpam-python
Version : 0.1.1
Upstream Author : Russell Stuart <russell-pampyt...@stuart.id.au>
* URL : http://www.stuart.id.au/russell/files/pam_python
* License : Eclipse Public License v1.0
Programming Lang: C, Python, etc.)
Description : a PAM Module that runs the Python interpreter to write pam
mo$
Perhaps the long package description can be based on this text from
the web page:
The pam_python PAM module runs the Python source file (aka Python
PAM module) it is given in the Python interpreter, making the PAM
module API available to it. This document describes the how the PAM
Module API is exposed to the Python PAM module. It does not describe
how to use the API. You must read the PAM module writers guide to
learn how to do that. To re-iterate: this document does not tell you
how to write PAM modules, it only tells you how to access that the
PAM module API from Python.
Writing PAM modules from Python incurs a large performance penalty
and requires Python to be installed, so it is not the best option
for writing modules that will be used widely. On the other hand
memory allocation / corruption problems can not be caused by bad
Python code, and a Python module is generally shorter and easier to
write than its C equivalent. This makes it ideal for the system
administrator who just wants to make use of the the PAM API for his
own ends while minimising the risk of introducing memory corruption
problems into every program using PAM.
-- System Information:
Debian Release: 5.0.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
--- End Message ---
--- Begin Message ---
Source: pam-python
Source-Version: 0.1.1-1
We believe that the bug you reported is fixed in the latest version of
pam-python, which is due to be installed in the Debian FTP archive:
libpam-python_0.1.1-1_i386.deb
to main/p/pam-python/libpam-python_0.1.1-1_i386.deb
pam-python_0.1.1-1.diff.gz
to main/p/pam-python/pam-python_0.1.1-1.diff.gz
pam-python_0.1.1-1.dsc
to main/p/pam-python/pam-python_0.1.1-1.dsc
pam-python_0.1.1.orig.tar.gz
to main/p/pam-python/pam-python_0.1.1.orig.tar.gz
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 578...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Petter Reinholdtsen <p...@debian.org> (supplier of updated pam-python 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...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Wed, 05 May 2010 10:25:24 +0200
Source: pam-python
Binary: libpam-python
Architecture: source i386
Version: 0.1.1-1
Distribution: unstable
Urgency: low
Maintainer: Russell Stuart <russell-deb...@stuart.id.au>
Changed-By: Petter Reinholdtsen <p...@debian.org>
Description:
libpam-python - Enables PAM modules to be written in Python
Closes: 578650
Changes:
pam-python (0.1.1-1) unstable; urgency=low
.
* Initial release based on package from upstream (Closes: #578650).
* Drop build depend on latex2html to avoid non-free dependency.
* Upgrade from debhelper 5 to 7.
* Update standards-version from 3.7.3 to 3.8.4. No changes needed.
Checksums-Sha1:
d4a53b72ca68c0984470757d09775c16a25419cc 1191 pam-python_0.1.1-1.dsc
a875ef7994a21dc88fa9ca61e5d045a784ce1a69 52560 pam-python_0.1.1.orig.tar.gz
acf0a0c979643fe255622eb16e387e726bed2322 5911 pam-python_0.1.1-1.diff.gz
2e68bf817bf3e6c892be096facf2303f168bd937 27628 libpam-python_0.1.1-1_i386.deb
Checksums-Sha256:
f4510dd0141b69e38df3b75e42fae738e61cb1744ea1bf02dde18560837d0dc0 1191
pam-python_0.1.1-1.dsc
53e6e92f00cd4f0d4a7db36f7c9df603851d2ca7446c03dac980d47295a8bf11 52560
pam-python_0.1.1.orig.tar.gz
1f0668dd440bcba8d78e5f43ee63206f783bd46805a6d12f70bc250b3b5cd816 5911
pam-python_0.1.1-1.diff.gz
b2e5f409135072299cfe417df751964dfec709439ef58553ca511e99be6aa282 27628
libpam-python_0.1.1-1_i386.deb
Files:
9d13463f7a7f0a580027b9e62372fec6 1191 python extra pam-python_0.1.1-1.dsc
d8c00d567f9740a6035d180c276fe562 52560 python extra
pam-python_0.1.1.orig.tar.gz
9f56ba1b3aedd22e89430a791b87ecfd 5911 python extra pam-python_0.1.1-1.diff.gz
516a60012320c9b9feef3bbef4af9222 27628 python extra
libpam-python_0.1.1-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iD8DBQFL4Tq620zMSyow1ykRAg9DAKCqhcWwHKDhv6k7dVapKGxtm40MmQCgrhyI
Tm/3wFWVz6F34mrdTjVNZqE=
=6wbA
-----END PGP SIGNATURE-----
--- End Message ---