Your message dated Mon, 30 Oct 2023 09:58:40 +0100
with message-id
<CAPybu_2V=GwqzmE-E4DydsNF7SFSd4n33+JRk=mqg34sg1x...@mail.gmail.com>
and subject line
has caused the Debian Bug report #1047616,
regarding yavta: Fails to build source after successful build
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1047616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yavta
Version: 0.0+git20220328.c7b5b75-1
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian...@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 yavta
> dpkg-buildpackage: info: source version 0.0+git20220328.c7b5b75-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Ricardo Ribalda Delgado
> <rica...@ribalda.com>
> dpkg-source --before-build .
> debian/rules clean
> dh clean
> dh_auto_clean
> make -j8 clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> Makefile:8: WARNING: Makefile support is deprecated, please switch to meson
> rm -f *.o
> rm -f yavta
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_clean
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building yavta using existing
> ./yavta_0.0+git20220328.c7b5b75.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
> yavta-0.0+git20220328.c7b5b75/yavta.1
> dpkg-source: error: aborting due to unexpected upstream changes, see
> /tmp/yavta_0.0+git20220328.c7b5b75-1.diff.L__wKs
> 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/yavta_0.0+git20220328.c7b5b75-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.
--- End Message ---
--- Begin Message ---
Tested on the last version and it works fine. Probably fixed with the
transition to meson
--- End Message ---
