Your message dated Mon, 07 Jan 2013 10:17:37 +0000
with message-id <[email protected]>
and subject line Bug#643227: fixed in nsscache 0.21.18-2
has caused the Debian Bug report #643227,
regarding nsscache: FTBFS: dpkg-buildpackage: error: dpkg-source -b
nsscache-0.8.8 gave error exit status 2
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.)
--
643227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643227
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: nsscache
Version: 0.8.8-1
Severity: important
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20110923 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> fakeroot debian/rules clean
> dh clean
> dh_testdir
> dh_auto_clean
> python2.7 setup.py clean -a
> running clean
> 'build/lib.linux-x86_64-2.7' does not exist -- can't clean it
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-2.7' does not exist -- can't clean it
> python setup.py clean -a
> /build/nsscache-4qjzMV/nsscache-0.8.8/nss_cache/caches/nssdb.py:25:
> DeprecationWarning: The popen2 module is deprecated. Use the subprocess
> module.
> import popen2
> running clean
> 'build/lib.linux-x86_64-2.6' does not exist -- can't clean it
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-2.6' does not exist -- can't clean it
> find . -name \*.pyc -exec rm {} \;
> dh_clean
> rm -f debian/nsscache.substvars
> rm -f debian/nsscache.*.debhelper
> rm -rf debian/nsscache/
> rm -f debian/*.debhelper.log
> rm -f debian/files
> find . \( \( -type f -a \
> \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
> -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
> -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
> -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
> \) -exec rm -f {} \; \) -o \
> \( -type d -a -name autom4te.cache -prune -exec rm -rf {} \; \)
> \)
> rm -f *-stamp
> dpkg-source -b nsscache-0.8.8
> dpkg-source: info: using source format `3.0 (quilt)'
> dpkg-source: info: building nsscache using existing
> ./nsscache_0.8.8.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
> nsscache-0.8.8/MANIFEST.in
> nsscache-0.8.8/nsscache.conf.5
> nsscache-0.8.8/setup.py
> dpkg-source: error: aborting due to unexpected upstream changes, see
> /tmp/nsscache_0.8.8-1.diff.ZVp3Z9
> dpkg-source: info: you can integrate the local changes with dpkg-source
> --commit
> dpkg-buildpackage: error: dpkg-source -b nsscache-0.8.8 gave error exit
> status 2
> ────────────────────────────────────────────────────────────────────────────────
> Build finished at 20110923-2224
The full build log is available from:
http://people.debian.org/~lucas/logs/2011/09/23/nsscache_0.8.8-1_lsid64.buildlog
This error is due to recent dpkg changes "“dpkg-source -b” on a “2.0”
or “3.0 (quilt)” source package will fail if it detects upstream changes
which are not managed by a quilt patch." [0]
[0] http://lists.debian.org/debian-devel-announce/2011/09/msg00001.html
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
--- End Message ---
--- Begin Message ---
Source: nsscache
Source-Version: 0.21.18-2
We believe that the bug you reported is fixed in the latest version of
nsscache, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jamie Wilkinson <[email protected]> (supplier of updated nsscache 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: Mon, 07 Jan 2013 09:56:48 +0000
Source: nsscache
Binary: nsscache
Architecture: source all
Version: 0.21.18-2
Distribution: unstable
Urgency: low
Maintainer: Jamie Wilkinson <[email protected]>
Changed-By: Jamie Wilkinson <[email protected]>
Description:
nsscache - asynchronously synchronise local NSS databases with remote direct
Closes: 643227
Changes:
nsscache (0.21.18-2) unstable; urgency=low
.
* Fix unmanaged files in tarball, by adding to debian/source/options.
(Closes: #643227)
Checksums-Sha1:
8408f9e6052da0e13196114e3ea0848da7f60558 1167 nsscache_0.21.18-2.dsc
82e199fd51462cb6e9a28e0a7f0104cf22cfef54 11896 nsscache_0.21.18-2.debian.tar.gz
455af4f7bb7f8888ddf68437f90c750fe3d6bb60 96260 nsscache_0.21.18-2_all.deb
Checksums-Sha256:
eac2fe07ff5b7b2f91b3a248bd704e9e7700b7f6ecbc7f2533f7fe72184eb315 1167
nsscache_0.21.18-2.dsc
c7c569115f3e72326a9eb9309b0bd24ab02f3d9b2147ee268d2455fa6df829f7 11896
nsscache_0.21.18-2.debian.tar.gz
6abb28627e9b4a49394097694fb3f7ab6ca8961b3939ee9054a3120e0a09f67f 96260
nsscache_0.21.18-2_all.deb
Files:
ee8ed83f0e3f3e5f2cb224ee45d32d82 1167 admin optional nsscache_0.21.18-2.dsc
cc8e80cdeae246ab2a05d2f14d44c6b3 11896 admin optional
nsscache_0.21.18-2.debian.tar.gz
79733e2117c1e1b09b8760079987069c 96260 admin optional
nsscache_0.21.18-2_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlDqnA4ACgkQ5u9oNyz9HDhN+wCfTsFsBB5gSYFbufFg3OAg+iOy
UW0An04aJeQ+gKBGRHJWI8iwJS0R/gRQ
=LdjJ
-----END PGP SIGNATURE-----
--- End Message ---
