Source: nagiosplugin
Version: 1.3.2-3
Severity: minor
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: [email protected]
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 nagiosplugin
> dpkg-buildpackage: info: source version 1.3.2-3
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Jelmer Vernooij <[email protected]>
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild --test-pytest
>    dh_auto_clean -O--buildsystem=pybuild -O--test-pytest
> I: pybuild base:275: python3.11 setup.py clean 
> /usr/lib/python3/dist-packages/setuptools/dist.py:745: 
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
> 
>         
> ********************************************************************************
>         Usage of dash-separated 'upload-dir' will not be supported in future
>         versions. Please use the underscore name 'upload_dir' instead.
> 
>         By 2023-Sep-26, you need to update your project and remove deprecated 
> calls
>         or your builds will no longer be supported.
> 
>         See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
>         
> ********************************************************************************
> 
> !!
>   opt = self.warn_dash_deprecation(opt, section)
> running clean
> removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_nagiosplugin/build' (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
>    dh_autoreconf_clean -O--buildsystem=pybuild -O--test-pytest
>    dh_clean -O--buildsystem=pybuild -O--test-pytest
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building nagiosplugin using existing 
> ./nagiosplugin_1.3.2.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: file 
> nagiosplugin-1.3.2/nagiosplugin.egg-info/SOURCES.txt has no final newline 
> (either original or modified version)
> dpkg-source: info: local changes detected, the modified files are:
>  nagiosplugin-1.3.2/nagiosplugin.egg-info/PKG-INFO
>  nagiosplugin-1.3.2/nagiosplugin.egg-info/SOURCES.txt
>  nagiosplugin-1.3.2/nagiosplugin.egg-info/dependency_links.txt
>  nagiosplugin-1.3.2/nagiosplugin.egg-info/not-zip-safe
>  nagiosplugin-1.3.2/nagiosplugin.egg-info/top_level.txt
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/nagiosplugin_1.3.2-3.diff.NJ8Qgr
> 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/nagiosplugin_1.3.2-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 via email to