Your message dated Fri, 19 Apr 2024 19:33:11 +0200
with message-id <1ab49d4a-4e3f-4dc6-846c-e454f4171...@rezozer.net>
and subject line gap-factint: Fails to build source after successful build
has caused the Debian Bug report #1044156,
regarding gap-factint: 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.)


-- 
1044156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gap-factint
Version: 1.6.3+ds-2
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 gap-factint
> dpkg-buildpackage: info: source version 1.6.3+ds-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Jerome Benoit 
> <calcu...@rezozer.net>
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean
>    dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building gap-factint using existing 
> ./gap-factint_1.6.3+ds.orig.tar.xz
> dpkg-source: info: local changes detected, the modified files are:
>  gap-factint-1.6.3+ds/doc/_entities.xml
>  gap-factint-1.6.3+ds/doc/title.xml
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/gap-factint_1.6.3+ds-2.diff.WM3j9D
> 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/gap-factint_1.6.3+ds-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.

--- End Message ---
--- Begin Message ---
Hi Lucas Nussbaum, thanks for your report.
I am closing the report as the package builds just fine right now.
Cheers, Jerome
--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Reply via email to