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

Bug#1044745: gammastep: Fails to build source after successful build



Source: gammastep
Version: 2.0.9-1
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 gammastep
> dpkg-buildpackage: info: source version 2.0.9-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Boyuan Yang <byang@debian.org>
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean
>    dh_auto_clean
> 	make -j8 distclean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> Making distclean in src
> make[2]: Entering directory '/<<PKGBUILDDIR>>/src'
> Making distclean in gammastep_indicator
> make[3]: Entering directory '/<<PKGBUILDDIR>>/src/gammastep_indicator'
> test -z "defs.py gammastep-indicator" || rm -f defs.py gammastep-indicator
> rm -rf .libs _libs
> rm -f *.lo
> test -z "" || rm -f 
> test . = "." || test -z "" || rm -f 
> rm -f Makefile
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/src/gammastep_indicator'
> make[3]: Entering directory '/<<PKGBUILDDIR>>/src'
> test -z "*-protocol.c *-client-protocol.h" || rm -f *-protocol.c *-client-protocol.h
> rm -rf .libs _libs
> rm -f *.o
> rm -f *.lo
> rm -f *.tab.c
> test -z "" || rm -f 
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
>  rm -f gammastep
> test . = "." || test -z "" || rm -f 
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/src'
> rm -f ./.deps/colorramp.Po
> rm -f ./.deps/config-ini.Po
> rm -f ./.deps/gamma-control-protocol.Po
> rm -f ./.deps/gamma-drm.Po
> rm -f ./.deps/gamma-dummy.Po
> rm -f ./.deps/gamma-randr.Po
> rm -f ./.deps/gamma-vidmode.Po
> rm -f ./.deps/gamma-wl.Po
> rm -f ./.deps/hooks.Po
> rm -f ./.deps/location-geoclue2.Po
> rm -f ./.deps/location-manual.Po
> rm -f ./.deps/options.Po
> rm -f ./.deps/orbital-authorizer-protocol.Po
> rm -f ./.deps/os-compatibility.Po
> rm -f ./.deps/pipeutils.Po
> rm -f ./.deps/redshift.Po
> rm -f ./.deps/signals.Po
> rm -f ./.deps/solar.Po
> rm -f ./.deps/systemtime.Po
> rm -f ./.deps/vlog.Po
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/src'
> Making distclean in po
> make[2]: Entering directory '/<<PKGBUILDDIR>>/po'
> rm -f *.pox gammastep.pot *.old.po cat-id-tbl.tmp
> rm -f .intltool-merge-cache
> rm -f Makefile Makefile.in POTFILES stamp-it
> rm -f *.mo *.msg *.cat *.cat.m *.gmo
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/po'
> make[2]: Entering directory '/<<PKGBUILDDIR>>'
> test -z "data/applications/gammastep.desktop data/applications/gammastep-indicator.desktop  data/appdata/gammastep-indicator.appdata.xml " || rm -f data/applications/gammastep.desktop data/applications/gammastep-indicator.desktop  data/appdata/gammastep-indicator.appdata.xml 
> rm -rf .libs _libs
> rm -f *.lo
> test -z "" || rm -f 
> rm -f config.h stamp-h1
> rm -f libtool config.lt
> test . = "." || test -z "" || rm -f 
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> rm -f cscope.out cscope.in.out cscope.po.out cscope.files
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> rm -f config.status config.cache config.log configure.lineno config.status.lineno
> rm -f Makefile
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building gammastep using existing ./gammastep_2.0.9.orig.tar.gz
> dpkg-source: warning: executable mode 0755 of 'compile' will not be represented in diff
> dpkg-source: warning: executable mode 0755 of 'config.guess' will not be represented in diff
> dpkg-source: warning: executable mode 0755 of 'config.rpath' will not be represented in diff
> dpkg-source: warning: executable mode 0755 of 'config.sub' will not be represented in diff
> dpkg-source: warning: executable mode 0755 of 'configure' will not be represented in diff
> dpkg-source: warning: executable mode 0755 of 'depcomp' will not be represented in diff
> dpkg-source: warning: executable mode 0755 of 'install-sh' will not be represented in diff
> dpkg-source: warning: executable mode 0755 of 'ltmain.sh' will not be represented in diff
> dpkg-source: warning: executable mode 0755 of 'missing' will not be represented in diff
> dpkg-source: warning: executable mode 0755 of 'py-compile' will not be represented in diff
> dpkg-source: info: local changes detected, the modified files are:
>  gammastep-2.0.9/ABOUT-NLS
>  gammastep-2.0.9/Makefile.in
>  gammastep-2.0.9/aclocal.m4
>  gammastep-2.0.9/compile
>  gammastep-2.0.9/config.guess
>  gammastep-2.0.9/config.h.in
>  gammastep-2.0.9/config.rpath
>  gammastep-2.0.9/config.sub
>  gammastep-2.0.9/configure
>  gammastep-2.0.9/depcomp
>  gammastep-2.0.9/install-sh
>  gammastep-2.0.9/ltmain.sh
>  gammastep-2.0.9/m4/codeset.m4
>  gammastep-2.0.9/m4/gettext.m4
>  gammastep-2.0.9/m4/glibc2.m4
>  gammastep-2.0.9/m4/glibc21.m4
>  gammastep-2.0.9/m4/iconv.m4
>  gammastep-2.0.9/m4/intdiv0.m4
>  gammastep-2.0.9/m4/intl.m4
>  gammastep-2.0.9/m4/intldir.m4
>  gammastep-2.0.9/m4/intlmacosx.m4
>  gammastep-2.0.9/m4/intltool.m4
>  gammastep-2.0.9/m4/intmax.m4
>  gammastep-2.0.9/m4/inttypes-pri.m4
>  gammastep-2.0.9/m4/inttypes_h.m4
>  gammastep-2.0.9/m4/lcmessage.m4
>  gammastep-2.0.9/m4/lib-ld.m4
>  gammastep-2.0.9/m4/lib-link.m4
>  gammastep-2.0.9/m4/lib-prefix.m4
>  gammastep-2.0.9/m4/libtool.m4
>  gammastep-2.0.9/m4/lock.m4
>  gammastep-2.0.9/m4/longlong.m4
>  gammastep-2.0.9/m4/ltoptions.m4
>  gammastep-2.0.9/m4/ltsugar.m4
>  gammastep-2.0.9/m4/ltversion.m4
>  gammastep-2.0.9/m4/lt~obsolete.m4
>  gammastep-2.0.9/m4/nls.m4
>  gammastep-2.0.9/m4/po.m4
>  gammastep-2.0.9/m4/printf-posix.m4
>  gammastep-2.0.9/m4/progtest.m4
>  gammastep-2.0.9/m4/size_max.m4
>  gammastep-2.0.9/m4/stdint_h.m4
>  gammastep-2.0.9/m4/uintmax_t.m4
>  gammastep-2.0.9/m4/visibility.m4
>  gammastep-2.0.9/m4/wchar_t.m4
>  gammastep-2.0.9/m4/wint_t.m4
>  gammastep-2.0.9/m4/xsize.m4
>  gammastep-2.0.9/missing
>  gammastep-2.0.9/po/Makefile.in.in
>  gammastep-2.0.9/po/Makevars.template
>  gammastep-2.0.9/po/Rules-quot
>  gammastep-2.0.9/po/boldquot.sed
>  gammastep-2.0.9/po/en@boldquot.header
>  gammastep-2.0.9/po/en@quot.header
>  gammastep-2.0.9/po/insert-header.sin
>  gammastep-2.0.9/po/quot.sed
>  gammastep-2.0.9/po/remove-potcdate.sin
>  gammastep-2.0.9/py-compile
>  gammastep-2.0.9/src/Makefile.in
>  gammastep-2.0.9/src/gammastep_indicator/Makefile.in
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/gammastep_2.0.9-1.diff.bJwm95
> 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/gammastep_2.0.9-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.


Reply to: