Your message dated Wed, 29 Jul 2026 10:20:51 +0000
with message-id <[email protected]>
and subject line Bug#1139446: fixed in pygobject 3.56.3-2
has caused the Debian Bug report #1139446,
regarding src:pygobject: fails to migrate to testing for too long: ftbfs on
s390x
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.)
--
1139446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1139446
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pygobject
Version: 3.56.2-1
Severity: serious
Control: close -1 3.56.3-1
Tags: sid forky ftbfs
User: [email protected]
Usertags: out-of-sync
X-Debbugs-CC: [email protected]
User: [email protected]
Usertags: s390x
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as having a Release Critical bug in
testing [1]. Your package src:pygobject has been trying to migrate for
31 days [2], hence this bug report. The current output of the migration
software for this package is copied to the bottom of this report and
should list the reason why the package is blocked.
If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Blocked packages can have impact on other packages,
which makes preparing for the release more difficult. The situation that
caused this bug report might even be the result of such an issue. We
expect maintainers to fix issues that hamper the migration of their
package in a timely manner. If your package in this situation due to
another package, consider helping out.
This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.
This bug submission immediately closes the bug with the version in
unstable, so if that version or a later version migrates, this bug will
no longer affect testing. This bug is also tagged to only affect sid and
forky, so it doesn't affect (old-)stable.
If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.
This bug report has been automatically generated. If you have any
comments with regards to the content or the process, please reach out to me.
Paul
[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=pygobject
Current text from [2]:
Migration status for pygobject (3.56.2-1 to 3.56.3-1): BLOCKED: Maybe
temporary, maybe blocked but Britney is missing information (check below)
Issues preventing migration:
∙ ∙ Missing build on s390x
∙ ∙ Autopkgtest deferred on s390x: missing arch:s390x build
∙ ∙ Autopkgtest for dasbus/1.7-2: amd64: Pass, arm64: Pass, i386: Pass,
loong64: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be
ignored)
∙ ∙ Autopkgtest for foomuuri/0.32-1: loong64: Pass ♻ (reference ♻)
∙ ∙ Autopkgtest for freedombox/26.8: loong64: Pass ♻
∙ ∙ Autopkgtest for hplip/3.26.4+dfsg0-2: amd64: Pass, arm64: Pass,
i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass
∙ ∙ Autopkgtest for openrazer/3.12.1+dfsg-1: loong64: No tests,
superficial or marked flaky ♻ (reference ♻)
∙ ∙ Autopkgtest for pygobject/3.56.3-1: amd64: No tests, superficial or
marked flaky ♻, arm64: No tests, superficial or marked flaky ♻
(reference ♻), i386: No tests, superficial or marked flaky ♻ (reference
♻), loong64: No tests, superficial or marked flaky ♻, ppc64el: No tests,
superficial or marked flaky ♻ (reference ♻), riscv64: No tests,
superficial or marked flaky ♻
∙ ∙ Lintian check waiting for test results on s390x - info
Additional info (not blocking):
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/p/pygobject.html
∙ ∙ Reproduced on amd64 - info
∙ ∙ Reproduced on arm64 - info
∙ ∙ Reproduced on armhf - info
∙ ∙ Reproduced on i386 - info
∙ ∙ 31 days old (needed 5 days)
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pygobject
Source-Version: 3.56.3-2
Done: Alessandro Astone <[email protected]>
We believe that the bug you reported is fixed in the latest version of
pygobject, 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.
Alessandro Astone <[email protected]> (supplier of updated
pygobject 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: Wed, 29 Jul 2026 12:00:59 +0200
Source: pygobject
Built-For-Profiles: derivative.ubuntu noudeb
Architecture: source
Version: 3.56.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers
<[email protected]>
Changed-By: Alessandro Astone <[email protected]>
Closes: 1139446
Changes:
pygobject (3.56.3-2) unstable; urgency=medium
.
* Team upload
* d/p: Backport fix for big-endian test failure.
This change stops trying to salvage broken GIR definitions with a
workaround that was incorrect on big-endian architectures, and instead
raises a python exception if that were to occur. (Closes: #1139446)
Checksums-Sha1:
fe1a0986745aaeb23f7904a7a3ef13d96b24f43e 2762 pygobject_3.56.3-2.dsc
89164b81abc8aac26ad7a36be2a5ae0b75954abb 27420 pygobject_3.56.3-2.debian.tar.xz
f4c0c9c6cd6ea2265cb8633f731ad6b7b966d012 12843
pygobject_3.56.3-2_source.buildinfo
Checksums-Sha256:
1c178e14c08c4a17e93c9df28c46a3d2e77b6c6d4db16a3a15bcae74b253bf31 2762
pygobject_3.56.3-2.dsc
1a50e94e43427a5a0cbcb708876a54c8c9b3d78493de969a615ca85c7f542061 27420
pygobject_3.56.3-2.debian.tar.xz
5318f25a711ffb37cca4180a04152b27a025c7ed12cb6280b780bde0e8d63afe 12843
pygobject_3.56.3-2_source.buildinfo
Files:
94c5b1581d4f46eec7902486d487d900 2762 python optional pygobject_3.56.3-2.dsc
e8f88810fe7c49d1411f3d700f0897b8 27420 python optional
pygobject_3.56.3-2.debian.tar.xz
96a49fcb6eff451e164fd76b5f54b1ac 12843 python optional
pygobject_3.56.3-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmppz8UACgkQ5mx3Wuv+
bH18Dw//RSBzmZRLzbPEDFOY+Zus2uI0ikIpz2GhLksEos9/ykjNDwFakin9ONUe
l10piJXRTWGb7jFfzCEN6xcBphXMCvE9kZrSBFRrRcIv8663Kg4ATa9s6/poRf8f
jhFFjGctx1qJjr/0G+XqioKTvQfxAbblOg9hKKztI9YHxo5yLsBoMM4aoXPiyySP
zG1LBXEAQwxi+PODm/XUpO6vsC9ldGiWDjYp3WCz5AEJHfdIIJNTjGWgZV7LgJbD
4dhsGr0tclu0LVPJUQdEW4dRXgWrqCmt3yje+SG3lMt7Da5698qJ5okav8e0foxV
0jX6QPmMW/VlKK1ZzWNWHeG1D1VfBr5AXjdevRKNtLA1Ap80DhtP0RQEBd0iJWST
ulZeuG6cPPyn4h+/3+XTKWa8VQVaO57RtVnbmYlH0ESX0Zlt9p7eOm8zuw9rB0XF
UDUzAkXRvCNYIkBTv/i2qiLyNjzzdyAuRIpG4VGWhxP/rmGEvWwGvuNRg6eRrh0z
oc5KboQ0T3B3f71MYfh3VRPOLulVROZO09k+ydUblArHzJUy2D9s59gPfUsr8VPJ
2xU+ToWsHzTLC2tcnvG8qdS+SUz7N4VvlJpAdgiuRR1yIFsYq9fDxfLj3aJigEpd
GOvSuTDJXWcPXBHT5ADi2aURBbndpBFR5VYDz20QbDiRpHRWl9Y=
=7XS5
-----END PGP SIGNATURE-----
pgpBftTGv0PDW.pgp
Description: PGP signature
--- End Message ---
