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

Bug#1046228: python-x2go: Fails to build source after successful build



Source: python-x2go
Version: 0.6.1.3-3
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 python-x2go
> dpkg-buildpackage: info: source version 0.6.1.3-3
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Mike Gabriel <sunweaver@debian.org>
>  dpkg-source --before-build .
>  debian/rules clean
> py3versions: no X-Python3-Version in control file, using supported versions
> test -x debian/rules
> rm -Rf docs/build/
> cd . && python3 setup.py clean -a
> running clean
> removing 'build/lib' (and everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.11' does not exist -- can't clean it
> removing 'build'
> rm -rf debian/python-module-stampdir
> find "/<<PKGBUILDDIR>>" -name '*.py[co]' -delete
> find "/<<PKGBUILDDIR>>" -name __pycache__ -type d -empty -delete
> find "/<<PKGBUILDDIR>>" -prune -name '*.egg-info' -exec rm -rf '{}' ';'
> dh_clean 
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: verifying ./python-x2go_0.6.1.3.orig.tar.gz.asc
> gpgv: Signature made Wed Jan  1 15:17:48 2020 UTC
> gpgv:                using RSA key 1AD23D1B8F087A35AB74BDE9F4A7678C9C6B0B2B
> gpgv: Note: signatures using the SHA1 algorithm are rejected
> gpgv: Can't check signature: Bad public key
> dpkg-source: warning: cannot verify upstream tarball signature for ./python-x2go_0.6.1.3.orig.tar.gz: no acceptable signature found
> dpkg-source: info: building python-x2go using existing ./python-x2go_0.6.1.3.orig.tar.gz
> dpkg-source: info: building python-x2go using existing ./python-x2go_0.6.1.3.orig.tar.gz.asc
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: file python-x2go-0.6.1.3/x2go.egg-info/SOURCES.txt has no final newline (either original or modified version)
> dpkg-source: info: local changes detected, the modified files are:
>  python-x2go-0.6.1.3/x2go.egg-info/PKG-INFO
>  python-x2go-0.6.1.3/x2go.egg-info/SOURCES.txt
>  python-x2go-0.6.1.3/x2go.egg-info/dependency_links.txt
>  python-x2go-0.6.1.3/x2go.egg-info/requires.txt
>  python-x2go-0.6.1.3/x2go.egg-info/top_level.txt
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/python-x2go_0.6.1.3-3.diff.dTQm7_
> 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/python-x2go_0.6.1.3-3_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: