Your message dated Mon, 10 Sep 2007 17:32:05 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431862: fixed in nss-updatedb 7-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: nss-updatedb
Version: 7-1.1
Severity: important

Hi there,

We have been using nss-updatedb on alioth (a slightly patched version to
temporarily work around a bug in nss-pgsql) and we have noticed that the
database updates are not atomic.  We frequently get exim panicking that
it can't find a user it has just decided to suid to, or svn commits
failing, or that sort of thing.

I'd like to work with you to resolve this - my first thought is to
switch to writing files in a temporary subdirectory, and then move them
across - while that doesn't eliminate the race condition, it should
lessen it.  

Take care,

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-xen-amd64
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)

Versions of packages nss-updatedb depends on:
ii  libc6                       2.3.6.ds1-13 GNU C Library: Shared libraries
ii  libdb4.3                    4.3.29-8     Berkeley v4.3 Database Libraries [

Versions of packages nss-updatedb recommends:
ii  libnss-db                    2.2.3pre1-2 NSS module for using Berkeley Data

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: nss-updatedb
Source-Version: 7-2

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

nss-updatedb_7-2.diff.gz
  to pool/main/n/nss-updatedb/nss-updatedb_7-2.diff.gz
nss-updatedb_7-2.dsc
  to pool/main/n/nss-updatedb/nss-updatedb_7-2.dsc
nss-updatedb_7-2_powerpc.deb
  to pool/main/n/nss-updatedb/nss-updatedb_7-2_powerpc.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.
Guido Guenther <[EMAIL PROTECTED]> (supplier of updated nss-updatedb 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, 10 Sep 2007 18:59:44 +0200
Source: nss-updatedb
Binary: nss-updatedb
Architecture: source powerpc
Version: 7-2
Distribution: experimental
Urgency: low
Maintainer: Guido Guenther <[EMAIL PROTECTED]>
Changed-By: Guido Guenther <[EMAIL PROTECTED]>
Description: 
 nss-updatedb - Cache name service directories in DB format
Closes: 431862 441483
Changes: 
 nss-updatedb (7-2) experimental; urgency=low
 .
   * link against pthread (Closes: #441483)
   * fill a temporary database, then replace the running one (Closes: #431862)
Files: 
 1fec06641b21e20359fa07984251dfe4 614 net extra nss-updatedb_7-2.dsc
 0cc9e1719be30ad058bc0a557f033ff3 94110 net extra nss-updatedb_7-2.diff.gz
 c7c0f8733c4d37f033d34995c8a2c5f6 12564 net extra nss-updatedb_7-2_powerpc.deb

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

iD8DBQFG5XzAn88szT8+ZCYRArQIAJ9f+Wt4VC8JgvvZGSSBn3uk9zxHrgCdEijH
TXIkL8gykos2VWG2bbgVvJs=
=zysJ
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to