[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1044178: gr-hpsdr: Fails to build source after successful build



Source: gr-hpsdr
Version: 3.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 gr-hpsdr
> dpkg-buildpackage: info: source version 3.0-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by A. Maitland Bottoms <bottoms@debian.org>
>  dpkg-source --before-build .
>  fakeroot debian/rules clean
> dh clean --with python3 --with numpy3
>    dh_auto_clean
> 	rm -rf obj-x86_64-linux-gnu
>    dh_clean
> 	rm -f debian/debhelper-build-stamp
> 	rm -rf debian/.debhelper/
> 	rm -f debian/gr-hpsdr.debhelper.log debian/libgnuradio-hpsdr1.0.0.debhelper.log
> 	rm -f -- debian/libgnuradio-hpsdr1.0.0.substvars debian/gr-hpsdr.substvars debian/gr-hpsdr.postinst.debhelper debian/gr-hpsdr.prerm.debhelper debian/files
> 	rm -fr -- debian/libgnuradio-hpsdr1.0.0/ debian/tmp/ debian/gr-hpsdr/
> 	find .  \( \( \
> 		\( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o -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 \( -path '*/.deps/*' -a -name '*.P' \) \
> 		\) -exec rm -f {} + \) -o \
> 		\( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) \)
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building gr-hpsdr using existing ./gr-hpsdr_3.0.orig.tar.xz
> dpkg-source: error: cannot represent change to docs/doxygen/doxyxml/__pycache__/__init__.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add docs/doxygen/doxyxml/__pycache__/__init__.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to docs/doxygen/doxyxml/__pycache__/base.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add docs/doxygen/doxyxml/__pycache__/base.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to docs/doxygen/doxyxml/__pycache__/doxyindex.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add docs/doxygen/doxyxml/__pycache__/doxyindex.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to docs/doxygen/doxyxml/__pycache__/text.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add docs/doxygen/doxyxml/__pycache__/text.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to docs/doxygen/doxyxml/generated/__pycache__/__init__.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add docs/doxygen/doxyxml/generated/__pycache__/__init__.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to docs/doxygen/doxyxml/generated/__pycache__/compound.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add docs/doxygen/doxyxml/generated/__pycache__/compound.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to docs/doxygen/doxyxml/generated/__pycache__/compoundsuper.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add docs/doxygen/doxyxml/generated/__pycache__/compoundsuper.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to docs/doxygen/doxyxml/generated/__pycache__/index.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add docs/doxygen/doxyxml/generated/__pycache__/index.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to docs/doxygen/doxyxml/generated/__pycache__/indexsuper.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add docs/doxygen/doxyxml/generated/__pycache__/indexsuper.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: unrepresentable changes to source
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 1
> 
> 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/gr-hpsdr_3.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: