Your message dated Tue, 13 Dec 2011 16:32:09 +0000
with message-id <[email protected]>
and subject line Bug#651948: fixed in dpatch 2.0.34
has caused the Debian Bug report #651948,
regarding FTBFS: patches not applied
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.)
--
651948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651948
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pinfo
Version: 0.6.9
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Trying to get pinfo to build for armhf, but I can see that right now
it doesn't build in unstable for amd64 either:
$ apt-get source pinfo
...
dpkg-source: warning: failed to verify signature on ./pinfo_0.6.9-5.dsc
dpkg-source: info: extracting pinfo in pinfo-0.6.9
dpkg-source: info: unpacking pinfo_0.6.9.orig.tar.gz
dpkg-source: info: applying pinfo_0.6.9-5.diff.gz
$ cd pinfo-0.6.9
$ dpkg-buildpackage -rfakeroot -b
dpkg-buildpackage: source package pinfo
dpkg-buildpackage: source version 0.6.9-5
dpkg-buildpackage: source changed by Bas Zoetekouw <[email protected]>
dpkg-buildpackage: host architecture amd64
dpkg-source --before-build pinfo-0.6.9
fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp install-stamp patch-stamp
dh_clean
rm -rf pinfo-0.6.9
debian/rules build
dh_testdir
tar xj --no-same-permissions -f pinfo-0.6.9.tar.bz2
rm -f pinfo-0.6.9/doc/pinfo.info
rm -f pinfo-0.6.9/doc/pinfo.1
dh_testdir
dpatch -d pinfo-0.6.9 apply-all
applying patch 01_pinforc to /home/steve/build/pinfo/pinfo-0.6.9/pinfo-0.6.9
...touch: cannot touch `src/pinforc.in': No such file or directory
failed.
make: *** [patch-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
Whether this is a bug in pinfo, dpkg-dev or dpatch I have no idea...
-- System Information:
Debian Release: 6.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: dpatch
Source-Version: 2.0.34
We believe that the bug you reported is fixed in the latest version of
dpatch, which is due to be installed in the Debian FTP archive:
dpatch_2.0.34.dsc
to main/d/dpatch/dpatch_2.0.34.dsc
dpatch_2.0.34.tar.gz
to main/d/dpatch/dpatch_2.0.34.tar.gz
dpatch_2.0.34_all.deb
to main/d/dpatch/dpatch_2.0.34_all.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.
Gergely Nagy <[email protected]> (supplier of updated dpatch
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: Tue, 13 Dec 2011 17:19:05 +0100
Source: dpatch
Binary: dpatch
Architecture: source all
Version: 2.0.34
Distribution: unstable
Urgency: high
Maintainer: Gergely Nagy <[email protected]>
Changed-By: Gergely Nagy <[email protected]>
Description:
dpatch - patch maintenance system for Debian source packages
Closes: 651948
Changes:
dpatch (2.0.34) unstable; urgency=high
.
* The magic that was supposed to reset the timestamps of patched files
failed to take the --workdir option into account. This has now been
corrected. (Closes: #651948)
.
Urgency high because this bug breaks any build that uses --workdir,
and has patchutils installed.
Checksums-Sha1:
2819679eefcdf00859d57b0f99ffcfc7e7f14330 1502 dpatch_2.0.34.dsc
7ce8ffc215fff2a92da6c441453e53ac24aec2c1 92098 dpatch_2.0.34.tar.gz
bca6ccebc2dca9eb4fff96fb32b82c67b5ea3566 95102 dpatch_2.0.34_all.deb
Checksums-Sha256:
dee560e3004edfbb023018b2b0bc6f6eb6c5058fc5d987b0901f727e0cabaa0b 1502
dpatch_2.0.34.dsc
eb8fac7967e969f48ead2d28d13cd8ba661d36f6b9af8be54d5d804c8068c392 92098
dpatch_2.0.34.tar.gz
c2049e3161890312b2da76270301606781d1680b61196602bf5b97eccf6a82f1 95102
dpatch_2.0.34_all.deb
Files:
63118c836e6f41615d4adc813878e14b 1502 vcs optional dpatch_2.0.34.dsc
0f6d082af3d5de4264ad78cd35bd54f5 92098 vcs optional dpatch_2.0.34.tar.gz
bd819071626803656a86b1da8194e802 95102 vcs optional dpatch_2.0.34_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBAgAGBQJO53v+AAoJEKwekLrEM/aP62YP/0UbFPfZulHmqVafqOunbPul
92DI/6Qur/465w0zXUIY5sHYyifEuhNVyP7IDgqFPiw1qw2M6TCS8SD10ovCdKLR
T5KBBFWC7wOpZQMa6pCh5quUhhDyf4jbLU0QJUdFsqT753VS2JOjWQhD7r5BJkkQ
Sr50BS1pFAolNG/3CLjyQ41OLqk6LBxYYJc/5GRxcZ2mi1j0L4N2CQqsUoNZ4NNG
t6nuNL9Z5Jjb91xkP7yGuKBz26GmUxr+AWV/GZ0qz1/+owQQtRYphWHZCqfcuC59
k3No+GDGra2pfgyGCCk4UaBPfsdXBK/jZKyTBmckYOiZVdA2IsVgkWdr5eqSLtKf
qIgT337u7fXRsz93ngn6PIUQbQz44DaYxVLsIBUjqyt3UNChYSvamDM8n1fDNGNF
Rsl/bbWgR90T+OBuVSbCfQSnYaPc4OJVImss0IKMfW0+HL0c2OV8C9agaBDEN67m
VRy/zvlY1GWX2uvv1XFyADFSaKVLueJNIQyGfquj5Rc8lzYv/AekxngDl/l8yvbX
zaLJj1+Ug0G4/GEQnqPABdfrjmL9rO4dH0bsxjhOgy1tyjYTEOIPZ5jnUJgFsEiX
6aCy7wY0h05wmuWYk4pG5uPPgNx5T1jmWUfOFE1LpGXcDmEHXuPsz49PMNHLqfmk
DrfUpgqrfl1NY6FoB7ab
=Ex6R
-----END PGP SIGNATURE-----
--- End Message ---
