Your message dated Mon, 29 Jan 2007 20:32:19 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#408887: fixed in pam-keyring 0.0.8-2
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: pam-keyring
Version: 0.0.8-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of pam-keyring_0.0.8-1 on bld-3 by sbuild/hppa 98
> Build started at 20070128-1617
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 5), autotools-dev, libpam0g-dev (>= 0.77),
> libgnome-keyring-dev (>= 0.4.8), dpatch, automake1.9, libtool
[...]
> checking whether ln -s works... yes
> checking for pkg-config... /usr/bin/pkg-config
> checking for GLIB - version >= 2.0.0... yes (version 2.12.6)
> checking for gnome-keyring-1... yes
> checking GNOME_KEYRING_CFLAGS... -I/usr/include/gnome-keyring-1
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
> checking GNOME_KEYRING_LIBS... -lgnome-keyring -lglib-2.0
> checking for gnome_keyring_unlock in -lgnome-keyring... yes
> checking security/pam_modules.h usability... yes
> checking security/pam_modules.h presence... yes
> checking for security/pam_modules.h... yes
> checking for pam_syslog in -lpam... no
> checking for gnome-keyring-daemon... /usr/bin/gnome-keyring-daemon
> checking for kill... no
> configure: error: kill executable not found in your path
> make: *** [config.status] Error 1
A full build log can be found at:
http://buildd.debian.org/build.php?arch=hppa&pkg=pam-keyring&ver=0.0.8-1
--- End Message ---
--- Begin Message ---
Source: pam-keyring
Source-Version: 0.0.8-2
We believe that the bug you reported is fixed in the latest version of
pam-keyring, which is due to be installed in the Debian FTP archive:
libpam-keyring_0.0.8-2_i386.deb
to pool/main/p/pam-keyring/libpam-keyring_0.0.8-2_i386.deb
pam-keyring_0.0.8-2.diff.gz
to pool/main/p/pam-keyring/pam-keyring_0.0.8-2.diff.gz
pam-keyring_0.0.8-2.dsc
to pool/main/p/pam-keyring/pam-keyring_0.0.8-2.dsc
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.
Laurent Bigonville <[EMAIL PROTECTED]> (supplier of updated pam-keyring 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.7
Date: Mon, 29 Jan 2007 20:14:08 +0100
Source: pam-keyring
Binary: libpam-keyring
Architecture: source i386
Version: 0.0.8-2
Distribution: unstable
Urgency: low
Maintainer: Laurent Bigonville <[EMAIL PROTECTED]>
Changed-By: Laurent Bigonville <[EMAIL PROTECTED]>
Description:
libpam-keyring - PAM module that unlock gnome keyring
Closes: 408887
Changes:
pam-keyring (0.0.8-2) unstable; urgency=low
.
* Add procps as a build dependency to fix FTBFS (Closes: #408887)
Files:
953f458fe89c0b4c7cec3bdd72d37f07 688 admin optional pam-keyring_0.0.8-2.dsc
755817eae74ba0fd59313b2fd01053a6 4345 admin optional
pam-keyring_0.0.8-2.diff.gz
eb020aa90a490d98d4b71499682d6b1f 15088 admin optional
libpam-keyring_0.0.8-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFvlSRAQwuptkwlkQRAk/uAJ9ARciT13u3FapPhHZI0hKa0CESMQCfXXv9
bB1XgBlII5EvQh6WbovH2Hk=
=fk40
-----END PGP SIGNATURE-----
--- End Message ---
