Your message dated Tue, 07 Jan 2025 19:08:07 +0000
with message-id <e1tvevv-003gw7...@fasolo.debian.org>
and subject line Bug#1086462: fixed in gcc-riscv64-unknown-elf 17
has caused the Debian Bug report #1086462,
regarding src:gcc-riscv64-unknown-elf: 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.)


-- 
1086462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-riscv64-unknown-elf
Version: 12
Severity: serious
Control: close -1 13
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:gcc-riscv64-unknown-elf 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=gcc-riscv64-unknown-elf

Current text from [2]:
Migration status for gcc-riscv64-unknown-elf (12 to 13): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
Issues preventing migration:
∙ ∙ missing build on mips64el
Additional info:
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-riscv64-unknown-elf.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Reproducible on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 31 days old (needed 5 days)

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: gcc-riscv64-unknown-elf
Source-Version: 17
Done: Keith Packard <kei...@keithp.com>

We believe that the bug you reported is fixed in the latest version of
gcc-riscv64-unknown-elf, 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 1086...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Keith Packard <kei...@keithp.com> (supplier of updated gcc-riscv64-unknown-elf 
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, 01 Dec 2024 11:55:17 -0800
Source: gcc-riscv64-unknown-elf
Architecture: source
Version: 17
Distribution: unstable
Urgency: medium
Maintainer: Keith Packard <kei...@keithp.com>
Changed-By: Keith Packard <kei...@keithp.com>
Closes: 1086462
Changes:
 gcc-riscv64-unknown-elf (17) unstable; urgency=medium
 .
   * Fix --disable-libstdcxx configure flag spelling.
   * Add -mlong-jump-table-offsets for m68k target.
   * Post gcc-14 migration upload. Closes: #1086462.
   * Apply Debian patches too.
Checksums-Sha1:
 c5c4284ca4baec364666b318298c6c868418fbad 1890 gcc-riscv64-unknown-elf_17.dsc
 a020c21b9960a3e552f86de57b961c2dab6c2ae5 7304 gcc-riscv64-unknown-elf_17.tar.xz
 85339d9cb98e889efcfae9164ce69993736b746b 7699 
gcc-riscv64-unknown-elf_17_amd64.buildinfo
Checksums-Sha256:
 b0935c19f865de548b5a2e94baad29045b0d2de18fa71ded068b42d5e2539ce0 1890 
gcc-riscv64-unknown-elf_17.dsc
 ea071a5e3ffde8a4f62030c355211210c5e3098e246bab445cc8c88039341b37 7304 
gcc-riscv64-unknown-elf_17.tar.xz
 f42eecae2874d29451471d90c31a8cb406c6ec89759a65e91f1cfe9b309d8d11 7699 
gcc-riscv64-unknown-elf_17_amd64.buildinfo
Files:
 5c827d3f01a084679ca11dd6687e455f 1890 devel optional 
gcc-riscv64-unknown-elf_17.dsc
 e688314d5ecd9295852ce862c3cc17f2 7304 devel optional 
gcc-riscv64-unknown-elf_17.tar.xz
 5f0094dc9069a8008b25f1468852dd3b 7699 devel optional 
gcc-riscv64-unknown-elf_17_amd64.buildinfo

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

iQIzBAEBCgAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAmd9d6wACgkQ2yIaaQAA
ABE4lg/9FAcTASU4h8MXPfg/FWthTJurca2kt232+GzhXnYm6V/ET6XZFjuSnBVx
Dh1qU632/BB8wfNDG13jcnyTxs8r5eElEBOjsHOuOcW8hxaCzZfgoZ2AhvbfJifi
1biPDCpxxNs9LijOSImVdTc1y7FmLxMIasBSU9iSo32gfv3etyWGtqm5cCROOj6R
2qNfG5f7RQdPZ/16vS5ngO7fFSKXQcAjjl2SnGZ17J2/AM781anOC9kNbH96WlSD
m7+lbQ130dI0dHB4A9yqxqaBepNzTxDd+7y8YFTZIyNYRJRjE22SXUaRpyMKkg+A
bcjHB/g/ZXv0dkZoqiYev7ZorFcS4yHJ98Ub0OywqJJxuoDczDFssylWlOrFlPoU
Fy9O3BSyqz2ce+7ew9kzPSkEG+UJdZs0g+/UE3U4loWgO5MCRxSq7GLIX/50naUV
c+WmUkwJrdXCr0GH4zThN18NguunNSKFNHpMrlqZ+boHhdMANy2iwRQbVHnZYLIK
1KWibAVKJ/SzybNsdXT5pWJsiq3QOAhGZZwz9yBNbiF/0bSObNCvVOu2Dlg32tbG
8bSrM4A6UIu1Nf93S92tQgc23dnEzpYQRimbWvwOhYPg1bhXg6aarRPBUXsinMCU
XKridA4tfRXkj8kiqL1HxefvpXdl2xMVXJ59IiTYcs33y4msPZI=
=WQDx
-----END PGP SIGNATURE-----

Attachment: pgptfwqJVKa4D.pgp
Description: PGP signature


--- End Message ---

Reply via email to