Bug#1044154: gcc-12: Fails to build source after successful build
Source: gcc-12
Version: 12.3.0-7
Severity: minor
Tags: trixie sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian-qa@lists.debian.org
Usertags: qa-doublebuild
Hi,
This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).
This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.
More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild
Relevant part of the build log:
> cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -S
> --------------------------------------------------------------------------------------------------------------------
>
> dpkg-buildpackage: info: source package gcc-12
> dpkg-buildpackage: info: source version 12.3.0-7
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Matthias Klose <doko@debian.org>
> dpkg-source --before-build .
> fakeroot debian/rules clean
> rm -rf stamps
> rm -rf gcc-12.3.0 newlib-4.3.0.20230120
> /usr/bin/make -f debian/rules2 clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_testdir
> rm -f pxxx status
> rm -f *-summary *-protocol testsuite-comparision summary-diff
> rm -f /<<PKGBUILDDIR>>/src/gcc/po/*.gmo
> rm -rf src-nvptx src-gcn
> rm -f debian/lib{gcc,objc,stdc++}{-v3,[0-9]}*.{{pre,post}{inst,rm},shlibs}
> fs=`echo debian/*BV* debian/*CXX* debian/*LC* debian/*MF* | sort -u`; \
> for f in $fs; do \
> [ -f $f ] || continue; \
> f2=$(echo $f | sed 's/BV/12/;s/CXX/6/;s/LC/1/;s/-CRB//;s/\.in$//'); \
> rm -f $f2; \
> done
> rm -f debian/lib*gcc-s1.symbols
> rm -f debian/lib*{atomic1,gfortran5,gomp1,itm1,quadmath0,stdc++6}.symbols
> find debian -maxdepth 1 -name '*-cross.symbols' -type l | xargs -r rm -f
> rm -f debian/gcc-{XX,ar,nm,ranlib}-12.1
> rm -f debian/shlibs.local debian/shlibs.common* debian/substvars.local
> rm -f debian/*.debhelper
> [ -d debian/bugs ] && /usr/bin/make -C debian/bugs clean
> make[1]: [debian/rules2:2219: clean] Error 1 (ignored)
> rm -f debian/README.libstdc++-baseline debian/README.Bugs debian/README.Debian.amd64
> rm -f debian/arch_binaries* debian/indep_binaries*
> rm -rf bin bin-gcn locales share
> rm -rf check-inst
> rm -f usage-*.svg
> rm -f installed-*.tar*
> dh_clean
> dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use)
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> rm -rf /<<PKGBUILDDIR>>/src* /<<PKGBUILDDIR>>/build* debian/tmp* html
> rm -f bootstrap-* first-move-stamp
> rm -f debian/*.tmp
> rm -f debian/soname-cache
> find debian -name '.#*' | xargs -r rm -f
> rm -f debian/patches/series*
> rm -rf .pc
> dh_clean
> dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use)
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building gcc-12 using existing ./gcc-12_12.3.0.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
> gcc-12-12.3.0/test-protocol2
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/gcc-12_12.3.0-7.diff.IzGppF
> dpkg-source: info: Hint: make sure the version in debian/changelog matches the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
>
> E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -S' failed to run.
The full build log is available from:
http://qa-logs.debian.net/2023/08/13/gcc-12_12.3.0-7_unstable.log
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
Reply to: