Your message dated Fri, 29 Mar 2024 00:50:01 +0000
with message-id <[email protected]>
and subject line Bug#1043626: fixed in apipkg 3.0.2-1
has caused the Debian Bug report #1043626,
regarding apipkg: 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 [email protected]
immediately.)
--
1043626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043626
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: apipkg
Version: 3.0.1-2
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 apipkg
> dpkg-buildpackage: info: source version 3.0.1-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Scott Talbert <[email protected]>
> dpkg-source --before-build .
> dpkg-source: info: using options from apipkg-3.0.1/debian/source/options:
> --extend-diff-ignore=^src/apipkg/version.py$
> debian/rules clean
> dh clean --buildsystem=pybuild --with python3
> dh_auto_clean -O--buildsystem=pybuild
> dh_autoreconf_clean -O--buildsystem=pybuild
> dh_clean -O--buildsystem=pybuild
> dpkg-source -b .
> dpkg-source: info: using options from apipkg-3.0.1/debian/source/options:
> --extend-diff-ignore=^src/apipkg/version.py$
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building apipkg using existing ./apipkg_3.0.1.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
> apipkg-3.0.1/src/apipkg/_version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see
> /tmp/apipkg_3.0.1-2.diff.kBacg3
> 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/apipkg_3.0.1-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 ---
Source: apipkg
Source-Version: 3.0.2-1
Done: Scott Talbert <[email protected]>
We believe that the bug you reported is fixed in the latest version of
apipkg, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Scott Talbert <[email protected]> (supplier of updated apipkg package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 28 Mar 2024 20:05:32 -0400
Source: apipkg
Architecture: source
Version: 3.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Scott Talbert <[email protected]>
Closes: 1043626
Changes:
apipkg (3.0.2-1) unstable; urgency=medium
.
* Update to new upstream release 3.0.2
* Update extend-diff-ignore to fix FTBFS double-build (Closes: #1043626)
Checksums-Sha1:
938442bde8864df1a4edad6b7619c95a4ff2ac66 2210 apipkg_3.0.2-1.dsc
4b26c6624b25923d7b94a12cea8ad456cca4ef86 14018 apipkg_3.0.2.orig.tar.gz
d6127f1691495991ad2b1422d6bb007093c09ae9 4208 apipkg_3.0.2-1.debian.tar.xz
6ac3864240edb0977e9f38cb0ad4e9ac9ef2b787 7304 apipkg_3.0.2-1_amd64.buildinfo
Checksums-Sha256:
35de090359f072cb4b773e2e5c0c5851aea47c50142823200a0d8e743c1de1f1 2210
apipkg_3.0.2-1.dsc
67345fd0446e5a24b50f42f2fc3e6a2cd5612379cd6944f68529886f188184ba 14018
apipkg_3.0.2.orig.tar.gz
a3426886d09c6707c8374bfbd9e84889604fae899ea8d6a18b5f8673d0f8b4a4 4208
apipkg_3.0.2-1.debian.tar.xz
500dcba235a4f7bcdcc27ad8a574befbd44c6d5c698855df02094bba953e1c3f 7304
apipkg_3.0.2-1_amd64.buildinfo
Files:
a146cae41cea0866685d70d2494cbe94 2210 python optional apipkg_3.0.2-1.dsc
5b22d0362478e34e36b2923d77a909c0 14018 python optional apipkg_3.0.2.orig.tar.gz
aecc05d73e3cc17b2be939ee8b76e064 4208 python optional
apipkg_3.0.2-1.debian.tar.xz
a956641dd1fbe6a77ee7d43f2bfb453c 7304 python optional
apipkg_3.0.2-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmYGCSIPHHN3dEB0ZWNo
aWUubmV0AAoJEFPVvGS1I3iieekP/Aqu9gA6sOifF5zMMHr1OVjKyfIkaxOD3OKU
YdVDoDPz8Wpvb75QMnmE2p6x1RBdMATCnFDtalzSC1wC3zLX9tEtqVXRvQCGb2CL
ppDS4Fx9sjrZLFakQAt9ujfa/PWwAyaQccQGzP4WFhLqpygbYRir/t49w2zUaK32
LzmmR/9G49a4gdUB99mrYDrxbUILIQu9wgASPqTR5sLVztZ19sGE4lpNZqaTy/cV
tMNSOADUB/IxXO+WpRs0MXwIPMmV5jMARF7+jdbeqGUQZ1oc9ccO5KzOKS1jy1/H
/15ukICt8b/yUtbV/jrvLAhf8e/kT4OMgCSl0ottjlxMNPHfddiU0hVMetzu11nV
QMa+1ZeGGOQt7z3B4hmHQjXWqS2UCrRrh8XP0Soo4Zr3lvuywARtmyD5zVmwvlTc
PXI/OeTuLn+EqzMWkstV13QW6UaLpkOZOuh7MDqWo47+Kd15dFoxcMiiLahtULXQ
JIoyWtCNFFIlwiomdlZTLWy8BNO3OFecYPlOq8d87mIfJusyV3eSAzLA9Yy3JIfi
Axro41wywyaiGOHdtNQHMdPl9UB1h22QSzfk/4nZi9+b6OuacuXeiW+bKokyoXTK
IQIVp/wRLlhgNbyqyJmFwJes45Z1nWfyVL4STMu1Dd//6FFJsxxrEhopkeAohy00
byHJEK5L
=8/tS
-----END PGP SIGNATURE-----
pgpFBlb4feoCo.pgp
Description: PGP signature
--- End Message ---
