Your message dated Fri, 30 Nov 2012 12:32:28 +0000
with message-id <e1teplc-00030o...@franck.debian.org>
and subject line Bug#694417: fixed in bbdb 2.36-3
has caused the Debian Bug report #694417,
regarding bbdb: package installation creates /root/.gnupg/*
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.)


-- 
694417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bbdb
Version: 2.36-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed that your package creates files in
/root. From the attached log (scroll to the bottom):

1m4.7s ERROR: FAIL: Package purging left files on system:
  /root/.gnupg/  not owned
  /root/.gnupg/gpg.conf  not owned
  /root/.gnupg/pubring.gpg       not owned
  /root/.gnupg/secring.gpg       not owned

Creating stuff in /root is a FHS and policy violation. (And of course
these files should not be deleted by maintainer scripts.)
But it is also an indication that the package operation may depend on
root's .gnupg configuration (and package installation might even fail if
that configuration is broken). That would be a case for "configuration
files not in /etc".


Cheers,

Andreas

Attachment: bbdb_2.36-2.log.gz
Description: GNU Zip compressed data


--- End Message ---
--- Begin Message ---
Source: bbdb
Source-Version: 2.36-3

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

Debian distribution maintenance software
pp.
Barak A. Pearlmutter <b...@debian.org> (supplier of updated bbdb 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: Fri, 30 Nov 2012 11:52:46 +0000
Source: bbdb
Binary: bbdb
Architecture: source all
Version: 2.36-3
Distribution: unstable
Urgency: low
Maintainer: Joerg Jaspert <jo...@debian.org>
Changed-By: Barak A. Pearlmutter <b...@debian.org>
Description: 
 bbdb       - The Insidious Big Brother Database (email rolodex) for Emacs
Closes: 694417
Changes: 
 bbdb (2.36-3) unstable; urgency=low
 .
   [ Sébastien Villemot ]
   * debian/bbdb.emacsen-install: no longer create /root/.gnupg during
     installation of the package. This is achieved by binding GNUPGHOME to a
     temporary directory during bytecode compilation (Closes: #694417)
Checksums-Sha1: 
 996ad4cf9b4d9472abb5fb255c894d40a2e46b8e 1299 bbdb_2.36-3.dsc
 be31e431cfd78eecb4c3670febcd31cc7464acb8 59955 bbdb_2.36-3.debian.tar.gz
 c330c0952bc62ade6a44d2b88a59afb5a3676447 812414 bbdb_2.36-3_all.deb
Checksums-Sha256: 
 f728c1da30454a291ca888210f68a6cd7685c70d8b05e48923126a12617ae863 1299 
bbdb_2.36-3.dsc
 76337a250b18d3bbfaa6df29846cbaa42d2588296a445aba00dbf51d860231db 59955 
bbdb_2.36-3.debian.tar.gz
 7b57a0d2bf75e93de7702e9cbed57d034515f08e48b7cd4d24468b9ddae8dfdd 812414 
bbdb_2.36-3_all.deb
Files: 
 bbd05e381e40027d32b5bd64f730982b 1299 mail optional bbdb_2.36-3.dsc
 69c85da859fe2a2fcc9be9167be1a815 59955 mail optional bbdb_2.36-3.debian.tar.gz
 7295bc62a61415310696dd9abcc9a21b 812414 mail optional bbdb_2.36-3_all.deb

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

iEYEARECAAYFAlC4pGMACgkQLz4Gnv7CP7LYLQCgnOtcLibwYnxN/jsR07nQSPs6
kUEAoIwr4VfRoJCwh7PY5w5H8EhdrDLf
=kWVk
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to