Your message dated Sat, 01 Aug 2026 20:34:58 +0000
with message-id <[email protected]>
and subject line Bug#1047423: fixed in pyerfa 2.0.1.5+ds-4
has caused the Debian Bug report #1047423,
regarding pyerfa: 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.)
--
1047423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047423
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pyerfa
Version: 2.0.0.3+ds-1
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 pyerfa
> dpkg-buildpackage: info: source version 2.0.0.3+ds-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Antonio Valentino
> <[email protected]>
> dpkg-source --before-build .
> debian/rules clean
> dh clean --with python3,sphinxdoc,numpy3 --buildsystem=pybuild
> debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> # dh_auto_clean
> rm -f -r build .pybuild
> rm -f -r .pytest_cache *.egg-info docs/api
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_autoreconf_clean -O--buildsystem=pybuild
> dh_clean -O--buildsystem=pybuild
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building pyerfa using existing
> ./pyerfa_2.0.0.3+ds.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
> pyerfa-2.0.0.3+ds/erfa/_version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see
> /tmp/pyerfa_2.0.0.3+ds-1.diff.6DVKH7
> 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/pyerfa_2.0.0.3+ds-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 ---
Source: pyerfa
Source-Version: 2.0.1.5+ds-4
Done: Antonio Valentino <[email protected]>
We believe that the bug you reported is fixed in the latest version of
pyerfa, 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.
Antonio Valentino <[email protected]> (supplier of updated pyerfa
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: Sat, 01 Aug 2026 18:07:07 +0000
Source: pyerfa
Architecture: source
Version: 2.0.1.5+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers
<[email protected]>
Changed-By: Antonio Valentino <[email protected]>
Closes: 1047423
Changes:
pyerfa (2.0.1.5+ds-4) unstable; urgency=medium
.
* debian/patches:
- New 0002-setuptools-scm-compat.patch (Closes: #1047423).
Checksums-Sha1:
9c2adc2b49c4663dfc0f18c93b08c462876b3555 2394 pyerfa_2.0.1.5+ds-4.dsc
0febd941dc54e3e2edd7ead49bc8a2431ff5b051 5588 pyerfa_2.0.1.5+ds-4.debian.tar.xz
e7c488ccdf4e2501ddc2ee499c961cbd6d197e7d 12364
pyerfa_2.0.1.5+ds-4_amd64.buildinfo
Checksums-Sha256:
49f3564beb9577f1e16ac1d70bc953029285899ee2ff7f8130ec35d44fa36471 2394
pyerfa_2.0.1.5+ds-4.dsc
f7370629a407ae60e8d33e1f9db4c2782a61557ef40e23fbee16112d93e28d81 5588
pyerfa_2.0.1.5+ds-4.debian.tar.xz
c41efed6985f29004b27b4b3e5a4e752806fbd20d4a313dcb9d574fa372ae494 12364
pyerfa_2.0.1.5+ds-4_amd64.buildinfo
Files:
e6b65b59ff9534ed11ef56f71a12d3e9 2394 python optional pyerfa_2.0.1.5+ds-4.dsc
fba1f7abdbca3aab7a598eadf66fd17d 5588 python optional
pyerfa_2.0.1.5+ds-4.debian.tar.xz
62234e2b8d2e860271496acfa611cd61 12364 python optional
pyerfa_2.0.1.5+ds-4_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJRBAEBCgA7FiEEO3DyCaX/1okDxHLF6/SKslePmBIFAmpuVSUdHGFudG9uaW8u
dmFsZW50aW5vQHRpc2NhbGkuaXQACgkQ6/SKslePmBLCmg/7B4KhOKx7Dg0MQgP9
/Hg6eu7qVOCSRPB8IAM0PrFi89DPEayJH7sYl7PXi1fG12V9yHArvEoEgMvRp+ZI
xGREGkOViAZZUctihF8C+dH5HRdX6JHa+00xkAp+dK7ooAhC3a2xTNp8s7y2xTQJ
ioIbfahMZLyY7bOaIxBP2+zFYUfPHm9c7ivzvxvrR9jk4AdS8xkU5Iy3vv5ilWu6
8VM06H1Szw2SxkTujtx+tG2VFGOD749jDrAWzy6BwJMqrDfkPB5D+8OPucIWJgQK
dKR1/nQUO0RnikvLuVrA6OAulQhZM5466/FGHjymKBnAbwVUKZ3LUIBbXMLJaRrm
Nli16RCCiQprcPJEte03IBRBZlTOxO9Ko27AZK8h5hltrHPaoupeAnBXuWXvd0hX
9JumYkOEjRLLMoZtJa0OUsQnO8tTGmAfqyreillTGsHpYA/1325aDw9b7mHIY4og
6Vo8habEDEbOS9rb1pT3Fx1v3y+VabU3Rd6jvtF3LIaLLLyVB+x1pCuFoI0gyB6e
C6+QqHriwIRoESexSlJe8NbeNKN9YSgilH37bHpcok3bQPW+xGLI0pKOjp/ik/gO
P5uQI/6O9MK/BRwVGLUlaoeGj5EdPIpK6xIfXfw6qbYESwSYgPTMtsMIieNoV8Xi
QqKnObHdYNK7L414OeTXuMjVGgM=
=SpQo
-----END PGP SIGNATURE-----
pgpguuya8iAdH.pgp
Description: PGP signature
--- End Message ---
