Your message dated Sun, 25 May 2025 18:19:35 +0000
with message-id <e1ujfwd-0059ql...@fasolo.debian.org>
and subject line Bug#1105809: fixed in magics++ 4.16.0+really4.15.5-1
has caused the Debian Bug report #1105809,
regarding src:magics++: fails to migrate to testing for too long
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.)
--
1105809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: magics++
Version: 4.15.5-1
Severity: serious
Control: close -1 4.16.0-1
Tags: sid trixie
User: release.debian....@packages.debian.org
Usertags: out-of-sync
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:magics++ 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. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or its
(reverse-)dependencies. We expect maintainers to fix issues that hamper
the migration of their package in a timely manner.
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
trixie, 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 and has only been sent
manually. 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=magics++
Current text from [2]:
Migration status for magics++ (4.15.5-1 to 4.16.0-1): BLOCKED:
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ Updating magics++ would introduce bugs in testing: #1103215
∙ ∙ missing build on amd64
∙ ∙ missing build on arm64
∙ ∙ missing build on ppc64el
∙ ∙ missing build on all
∙ ∙ arch:all not built yet, autopkgtest delayed
Additional info:
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/m/magics++.html
∙ ∙ Waiting for reproducibility test results on arm64 - info ♻ ∙ ∙
Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Waiting
for reproducibility test results on i386 - info ♻ ∙ ∙ 30 days old
(needed 10 days)
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: magics++
Source-Version: 4.16.0+really4.15.5-1
Done: Bastian Germann <b...@debian.org>
We believe that the bug you reported is fixed in the latest version of
magics++, 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 1105...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bastian Germann <b...@debian.org> (supplier of updated magics++ 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, 25 May 2025 19:53:32 +0200
Source: magics++
Architecture: source
Version: 4.16.0+really4.15.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Bastian Germann <b...@debian.org>
Closes: 1105809
Changes:
magics++ (4.16.0+really4.15.5-1) unstable; urgency=medium
.
* Team upload
* Reupload 4.15.5. Closes: #1105809
Checksums-Sha1:
5a9c7aac5342bae831a8800d9f7a816357a0cff7 2747
magics++_4.16.0+really4.15.5-1.dsc
95252b91174883a032a5122c2ba570998e7b45af 22894872
magics++_4.16.0+really4.15.5.orig.tar.xz
c193096dcd8cc11b46d12b93fd1f16b484d21c4f 19420
magics++_4.16.0+really4.15.5-1.debian.tar.xz
246d07d91ba47a36a3c7d0b137903c2c9c873ce8 6078
magics++_4.16.0+really4.15.5-1_source.buildinfo
Checksums-Sha256:
e18c6f804394b6a127c8b144adf792759a381adbe4285cdbb6158f1e5f58c06d 2747
magics++_4.16.0+really4.15.5-1.dsc
093d6cca1c396e686440d0745e33d6b1aeabd6988bba6b586e635712c99929c1 22894872
magics++_4.16.0+really4.15.5.orig.tar.xz
93f0c62c80cdbe53b19581d69cd9a28932cd4dd410443c59ff789f9552702f69 19420
magics++_4.16.0+really4.15.5-1.debian.tar.xz
e6aee5c332444e3cbc1be35d201a0bc9a30fbbd245439297f6a589445eeede56 6078
magics++_4.16.0+really4.15.5-1_source.buildinfo
Files:
ba86e04ed86f71c7198ef95d92a2cf04 2747 science optional
magics++_4.16.0+really4.15.5-1.dsc
3f334a411f1abdd8b691c2e69fe529b4 22894872 science optional
magics++_4.16.0+really4.15.5.orig.tar.xz
9ef55ce1328b2225e0e15577b4f77fa7 19420 science optional
magics++_4.16.0+really4.15.5-1.debian.tar.xz
7189cd5e6a727f9d892001030209e1f3 6078 science optional
magics++_4.16.0+really4.15.5-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmgzWpEQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFDMJC/9i6dtNgsRwIhGbW53TeDvEmeP+ulFaAJim
o8ABWuGfhnmH7/+xKB1K5h0g8o/gh5bgmhmGg+KdxyfDxU0P1l43xYWZeYvAFYD3
VV/Ni2mCIvtWk+tC9FKVVIxdMhmbZQBfaJ8jxfavWwoKwnM/T9aH5+XihSA1Rn0T
ebYlXgOSgkIgJseHouJ0zxT77SYzCtzx9GwBvolIWtNdMdDegXahfFdQpa5qLF3x
oHV/RFP3Rnu1L3anSzXKRX9fdLk8IjCmglHXtC4A/ZqNGaPoLdLEFlVw6xEi3h13
8apHzLH3ujSBTLMUvBgtmG3zdJGf4h0HAeUJXf1yfu0Q7F0qroSA6Xg2vZZl9dn5
fkAsyO6WCx1AIshSCioue18L1udRrnYeQRxERg+oGGnnOgrvkrFqkNmYk8BOTiJb
Pbrz9Fu1/qY0Cx2sKe8DkaVTTKf1vrxwyGUFcU7bCwHXyDsY7TArK7dpi0KzwYqX
VTDeCZyXdkwDp9Lj1JEIGWHNdrIybNQ=
=pboc
-----END PGP SIGNATURE-----
pgpkIVStOFZfi.pgp
Description: PGP signature
--- End Message ---
