Your message dated Sun, 17 Jul 2022 10:48:54 +0000
with message-id <e1od1pw-000fub...@fasolo.debian.org>
and subject line Bug#1015086: fixed in asdf-coordinates-schemas 0.1.0-3
has caused the Debian Bug report #1015086,
regarding asdf-coordinates-schemas: FTBFS: dpkg-buildpackage: error: 
dpkg-source -b . subprocess returned exit status 2
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.)


-- 
1015086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asdf-coordinates-schemas
Version: 0.1.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>    dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:239: python3.9 setup.py clean 
> running clean
> removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build' (and everything under 
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> I: pybuild base:239: python3.10 setup.py clean 
> running clean
> removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build' (and everything 
> under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.10' does not exist -- can't clean it
>    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 asdf-coordinates-schemas using existing 
> ./asdf-coordinates-schemas_0.1.0.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
>  asdf-coordinates-schemas-0.1.0/src/asdf_coordinates_schemas/_version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/asdf-coordinates-schemas_0.1.0-2.diff.sx3TIH
> 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
> --------------------------------------------------------------------------------
> Build finished at 2022-07-16T06:05:59Z


The full build log is available from:
http://qa-logs.debian.net/2022/07/16/asdf-coordinates-schemas_0.1.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220716&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking 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: asdf-coordinates-schemas
Source-Version: 0.1.0-3
Done: Ole Streicher <oleb...@debian.org>

We believe that the bug you reported is fixed in the latest version of
asdf-coordinates-schemas, 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 1015...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ole Streicher <oleb...@debian.org> (supplier of updated 
asdf-coordinates-schemas 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 17 Jul 2022 12:26:52 +0200
Source: asdf-coordinates-schemas
Architecture: source
Version: 0.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 
<debian-astro-maintain...@lists.alioth.debian.org>
Changed-By: Ole Streicher <oleb...@debian.org>
Closes: 1015086
Changes:
 asdf-coordinates-schemas (0.1.0-3) unstable; urgency=medium
 .
   * Add version.py to d/clean (Closes: #1015086)
   * Push Standards-Version to 4.6.1. No changes needed
Checksums-Sha1:
 d786175e4d09c925c1e8338d2ebd1842ddd7f900 2299 
asdf-coordinates-schemas_0.1.0-3.dsc
 3c2e09028433e8070a2c8cc09b9ab04745b24c3d 2508 
asdf-coordinates-schemas_0.1.0-3.debian.tar.xz
Checksums-Sha256:
 ddf8650e8cb6eb166750b7ad9dab42b66bb0489378cee58f46a668bed593e7ad 2299 
asdf-coordinates-schemas_0.1.0-3.dsc
 2cee52b1c5d492528dd4b5cf8b1c679c366eb8e6467d2a2d163ae89aeb3557c3 2508 
asdf-coordinates-schemas_0.1.0-3.debian.tar.xz
Files:
 abe0b9e2fa0277b685a9364b72644263 2299 python optional 
asdf-coordinates-schemas_0.1.0-3.dsc
 7999bff7df0d98c1abc05bdf82763a70 2508 python optional 
asdf-coordinates-schemas_0.1.0-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAmLT5LcACgkQmk9WvbkO
GL01VxAAm1IzGidS3dc9kLnMtXtWdboNH94OPyP9UaLFXstx8YhAC/Uwj8Xc+ZE8
/M5WBq1cjhf+WYfRcFcMWYPDS9koJEkDtEYUR4bCdwwCCcIA+MJJCAka4DlHeJeO
xqyAXxi42TcLvsSRL6APeGMVCE+Ufnf7OLa7o3bg4U0LKxurl6TewYPVJkH2Byhk
DBPcrbCfLA6rkAclwPIT7kqcxCtd8+9Pj8ubSZmrcV0CIr9ddyLvMfOoZWOVJG2y
Qj//evX0FIUS2AihQMLy6J2a3FfJ9fAKxrsmc4xbyHGG9OiC/Hli2v84QVmkoLVD
HbxlvJDnfy+SglDCFse8o05R5cKAYdy8BUXLH5e+XXt4larIxDuTa7WTxmq3Z9Xj
7Q+gNrJMAMEGOihAFO2VV3GHjF1vwhi5W5X4Fi1QjKFFyzctJR1lDrSwa/KEHtmt
9uhtbHPIyTpRYW0razT23z9RCuLXHAzmJygqlXWiq5/rrG19Ux0Qtfs2W0qf1ZaC
e1nSQjT88Op32qMvNiH9hgnACbjQdwXNUZRLRgEExuiNx33ZNUR4MXcp01TupFW7
RsOWrRr10SpCQ8AztX8vwoWcJte9oXbP478eIVRcTAKgZnHQxhGV3S5lOl5GUDHk
j4E8z6qCXVXTyIFGHbueR97bDrGM+04TBOfHFa3F2SLYBnP5v5E=
=wseO
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to