Bug#1046361: upse: Fails to build source after successful build
Source: upse
Version: 1.0.0-2
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 upse
> dpkg-buildpackage: info: source version 1.0.0-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Michael Ablassmeier <abi@debian.org>
> dpkg-source --before-build .
> fakeroot debian/rules clean
> dh clean
> dh: warning: Compatibility levels before 10 are deprecated (level 8 in use)
> debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> [ ! -f buildsys.mk ] || dh_auto_clean
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 8 in use)
> make -j1 distclean
> make[2]: Entering directory '/<<PKGBUILDDIR>>'
> [K[0;36mEntering directory [1;36msrc[0;36m.[0m
> make[3]: Entering directory '/<<PKGBUILDDIR>>/src'
> [K[0;36mEntering directory [1;36mlibupse[0;36m.[0m
> make[4]: Entering directory '/<<PKGBUILDDIR>>/src/libupse'
> [K[0;34mDeleted [1;34mupse_string.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_util.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_unpack_psf.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_bios_manager.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_r3000_bytecode_evaluator.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_r3000_abstract.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_ps1_executive.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_ps1_counters.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_ps1_gpu.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_ps1_hal.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_ps1_bios_base.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_ps1_memory_manager.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_ps1_dma_manager.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_ps1_spu_base.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_ps1_spu_dma_handler.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_ps1_spu_register_io.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_ps1_spu_reverb.o[0;34m.[0m
> [K[0;34mDeleted [1;34mupse_ps1_spu_adsr_filter.o[0;34m.[0m
> [K[0;34mDeleted [1;34m.deps[0;34m.[0m
> make[4]: Leaving directory '/<<PKGBUILDDIR>>/src/libupse'
> [K[0;36mLeaving directory [1;36mlibupse[0;36m.[0m
> [K[0;36mEntering directory [1;36mupse123[0;36m.[0m
> make[4]: Entering directory '/<<PKGBUILDDIR>>/src/upse123'
> [K[0;34mDeleted [1;34mupse123_main.o[0;34m.[0m
> [K[0;34mDeleted [1;34m.deps[0;34m.[0m
> make[4]: Leaving directory '/<<PKGBUILDDIR>>/src/upse123'
> [K[0;36mLeaving directory [1;36mupse123[0;36m.[0m
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/src'
> [K[0;36mLeaving directory [1;36msrc[0;36m.[0m
> [K[0;36mEntering directory [1;36msrc[0;36m.[0m
> make[3]: Entering directory '/<<PKGBUILDDIR>>/src'
> [K[0;36mEntering directory [1;36mlibupse[0;36m.[0m
> make[4]: Entering directory '/<<PKGBUILDDIR>>/src/libupse'
> make[4]: Leaving directory '/<<PKGBUILDDIR>>/src/libupse'
> [K[0;36mLeaving directory [1;36mlibupse[0;36m.[0m
> [K[0;36mEntering directory [1;36mupse123[0;36m.[0m
> make[4]: Entering directory '/<<PKGBUILDDIR>>/src/upse123'
> make[4]: Leaving directory '/<<PKGBUILDDIR>>/src/upse123'
> [K[0;36mLeaving directory [1;36mupse123[0;36m.[0m
> [K[0;36mEntering directory [1;36mlibupse[0;36m.[0m
> make[4]: Entering directory '/<<PKGBUILDDIR>>/src/libupse'
> [K[0;34mDeleted [1;34mlibupse.so[0;34m.[0m
> make[4]: Leaving directory '/<<PKGBUILDDIR>>/src/libupse'
> [K[0;36mLeaving directory [1;36mlibupse[0;36m.[0m
> [K[0;36mEntering directory [1;36mupse123[0;36m.[0m
> make[4]: Entering directory '/<<PKGBUILDDIR>>/src/upse123'
> [K[0;34mDeleted [1;34mupse123[0;34m.[0m
> make[4]: Leaving directory '/<<PKGBUILDDIR>>/src/upse123'
> [K[0;36mLeaving directory [1;36mupse123[0;36m.[0m
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/src'
> [K[0;36mLeaving directory [1;36msrc[0;36m.[0m
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_clean
> dh_clean: warning: Compatibility levels before 10 are deprecated (level 8 in use)
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building upse using existing ./upse_1.0.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: executable mode 0755 of 'config.status' will not be represented in diff
> dpkg-source: info: local changes detected, the modified files are:
> upse-1.0.0/buildsys.mk
> upse-1.0.0/config.h
> upse-1.0.0/config.log
> upse-1.0.0/config.status
> upse-1.0.0/extra.mk
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/upse_1.0.0-2.diff.Hysa3c
> 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/upse_1.0.0-2_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: