Your message dated Sun, 13 May 2012 16:40:52 +0300
with message-id <20120513134052.GA1011@lisko>
and subject line fixed
has caused the Debian Bug report #643112,
regarding fakeroot: FTBFS: dpkg-buildpackage: error: dpkg-source -b
fakeroot-1.18 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.)
--
643112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643112
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: fakeroot
Version: 1.18-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
> test -f debian/rules
> test root = "`whoami`"
> test -f debian/rules
> rm -rf obj-sysv obj64-sysv obj-tcp obj64-tcp
> rm -f build-stamp build-biarch-stamp
> cd obj-sysv && /usr/bin/make distclean
> /bin/bash: line 0: cd: obj-sysv: No such file or directory
> make: [clean] Error 1 (ignored)
> cd obj-tcp && /usr/bin/make distclean
> /bin/bash: line 0: cd: obj-tcp: No such file or directory
> make: [clean] Error 1 (ignored)
> cd obj64-sysv && /usr/bin/make distclean
> /bin/bash: line 0: cd: obj64-sysv: No such file or directory
> make: [clean] Error 1 (ignored)
> cd obj64-tcp && /usr/bin/make distclean
> /bin/bash: line 0: cd: obj64-tcp: No such file or directory
> make: [clean] Error 1 (ignored)
> rm -rf .deps
> rm -f debian/substvars debian/files
> rm -rf debian/tmp obj obj64 autom4te.cache
> 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 -name core -o \( -path
> \*/.deps/\* -a -name \*.P \) \) -exec rm -f {} \;
> dpkg-source -b fakeroot-1.18
> dpkg-source: info: using source format `3.0 (quilt)'
> dpkg-source: info: building fakeroot using existing
> ./fakeroot_1.18.orig.tar.bz2
> dpkg-source: info: local changes detected, the modified files are:
> fakeroot-1.18/build-aux/libtool.m4
> fakeroot-1.18/build-aux/ltoptions.m4
> fakeroot-1.18/build-aux/ltsugar.m4
> fakeroot-1.18/build-aux/ltversion.m4
> fakeroot-1.18/build-aux/lt~obsolete.m4
> fakeroot-1.18/doc/Makefile.am
> fakeroot-1.18/doc/Makefile.in
> fakeroot-1.18/doc/po4a/po/es.po
> fakeroot-1.18/doc/po4a/po/fakeroot.pot
> fakeroot-1.18/doc/po4a/po/fr.po
> fakeroot-1.18/doc/po4a/po/nl.po
> fakeroot-1.18/doc/po4a/po/sv.po
> dpkg-source: error: aborting due to unexpected upstream changes, see
> /tmp/fakeroot_1.18-1.diff.K6AoTU
> dpkg-source: info: you can integrate the local changes with dpkg-source
> --commit
> dpkg-buildpackage: error: dpkg-source -b fakeroot-1.18 gave error exit status
> 2
> ────────────────────────────────────────────────────────────────────────────────
> Build finished at 20110923-2255
The full build log is available from:
http://people.debian.org/~lucas/logs/2011/09/23/fakeroot_1.18-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 ---
Version: 1.18.3-1
I tested build using pbuilder. Some warnings are printed during build but
they aren't fatal.
--- End Message ---
