Bug#1043655: cme: Fails to build source after successful build
Lucas Nussbaum
lucas at debian.org
Sun Aug 13 14:17:57 BST 2023
Source: cme
Version: 1.038-1
Severity: minor
Tags: trixie sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian-qa at 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 cme
> dpkg-buildpackage: info: source version 1.038-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Dominique Dumont <dod at debian.org>
> dpkg-source --before-build .
> debian/rules clean
> dh clean
> dh_auto_clean
> /usr/bin/perl Build realclean --allow_mb_mismatch 1
> Cleaning up build files
> Cleaning up configuration files
> debian/rules override_dh_clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_clean
> rm -rf /<<PKGBUILDDIR>>/debian/build
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building cme using existing ./cme_1.038.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
> cme-1.038/wr_root/popcon1/etc/popularity-contest.conf
> cme-1.038/wr_root/popcon1/etc/popularity-contest.conf.old
> cme-1.038/wr_root/popcon1/my-script.cme
> cme-1.038/wr_root/popcon1/my-script0.cme
> cme-1.038/wr_root/popcon1/my-script1.cme
> cme-1.038/wr_root/popcon1/my-script10.cme
> cme-1.038/wr_root/popcon1/my-script2.cme
> cme-1.038/wr_root/popcon1/my-script3.cme
> cme-1.038/wr_root/popcon1/my-script4.cme
> cme-1.038/wr_root/popcon1/my-script5.cme
> cme-1.038/wr_root/popcon1/my-script6.cme
> cme-1.038/wr_root/popcon1/my-script7.cme
> cme-1.038/wr_root/popcon1/my-script8.cme
> cme-1.038/wr_root/popcon1/my-script9.cme
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/cme_1.038-1.diff.0xEjDz
> 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/cme_1.038-1_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.
More information about the pkg-perl-maintainers
mailing list