Your message dated Wed, 21 Jan 2026 12:19:26 +0000
with message-id <[email protected]>
and subject line Bug#1123864: fixed in cpufetch 1.07-2
has caused the Debian Bug report #1123864,
regarding src:cpufetch: fails to migrate to testing for too long: FTBFS on 
ppc64el
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.)


-- 
1123864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123864
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: cpufetch
Version: 1.06-2
Severity: serious
Control: close -1 1.07-1
Tags: sid forky ftbfs
User: [email protected]
Usertags: out-of-sync
User: [email protected]
X-Debbugs-CC: [email protected]
Usertags: ppc64el

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:cpufetch has been trying to migrate for 32 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 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 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=cpufetch

Current text from [2]:
Migration status for cpufetch (1.06-2 to 1.07-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
Issues preventing migration:
∙ ∙ Missing build on ppc64el
∙ ∙ Autopkgtest deferred on ppc64el: missing arch:ppc64el build
∙ ∙ Lintian check waiting for test results on ppc64el - info
Additional info (not blocking):
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpufetch.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ 32 days old (needed 5 days)

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: cpufetch
Source-Version: 1.07-2
Done: Clay Stan <[email protected]>

We believe that the bug you reported is fixed in the latest version of
cpufetch, 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.
Clay Stan <[email protected]> (supplier of updated cpufetch 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, 21 Jan 2026 06:55:22 -0500
Source: cpufetch
Architecture: source
Version: 1.07-2
Distribution: unstable
Urgency: medium
Maintainer: Clay Stan <[email protected]>
Changed-By: Clay Stan <[email protected]>
Closes: 1123864
Changes:
 cpufetch (1.07-2) unstable; urgency=medium
 .
   * Fix the build on ppc64 (Closes: 1123864).
Checksums-Sha1:
 d1a8f2c883d5c7bb7f2fe79297f579a97d0269a3 1824 cpufetch_1.07-2.dsc
 f0920aec934bf432cb265d6bc3a0e6ea61688bc3 5100 cpufetch_1.07-2.debian.tar.xz
 bff213f4ec2997cdb41f08f8d515d6b45af2f292 5970 cpufetch_1.07-2_amd64.buildinfo
Checksums-Sha256:
 5a19b40d71195488810b873c9d08242aef7413e4a47cf74d6a51cea767a99d27 1824 
cpufetch_1.07-2.dsc
 9241003317a9eb7e34169955f5f6e6e68509c4d10bd1b436f0fd479f182206f7 5100 
cpufetch_1.07-2.debian.tar.xz
 667e848a13c74a3b7300271dec27d8a5c5f435097933bac69244efd411bba0a9 5970 
cpufetch_1.07-2_amd64.buildinfo
Files:
 b8c4b1c0a661eb48586f237ec00a0c7c 1824 utils optional cpufetch_1.07-2.dsc
 59719092180d2f8a4ee0ef10b9332930 5100 utils optional 
cpufetch_1.07-2.debian.tar.xz
 e3f687be19802de6bb8193d99344c790 5970 utils optional 
cpufetch_1.07-2_amd64.buildinfo

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

iQIzBAEBCgAdFiEERYjLWMuJNfrH3QLQI8D8YLBAvsMFAmlwv/oACgkQI8D8YLBA
vsOvxQ//QA4WZyLAMuanAtXEq1s7+RI6tAXPCYaxx7urDmaWBMo9VTO5qOccxPRv
CUHlIKHyFDRwQYhk0MciYJodIlg46pZTecNkxO9YnMMBUkGeKLp5Zf5WCAPZJj8x
I2wtxilxp8Pmot373BNQYQMk7eExQNHrMmKDu8wnoAWO6MSuc6l03zabHFk+xLm+
/j8ccrjRD39jFVfs3ZKWvxT3Ekje3ivia2Mm/nndXcCyMXONRnC/YOBQvWRRm1wP
5kh6erV8/Yga2UqQrVNl0q8w2m63THDzjH4GIfWvolSIEI/aefhhkrGWGKGR5IYp
LrjW+ypGDgVaFgAw3Ru6dcmYs5/xVpzksze+BGP+mQCAdKSNOwDouEeRAiweKbAQ
Z0mGbyS94CSQJnzaoyV4wRqfqjQDWyIEfFOQLoWHY12cZvFMq1m4govfpOtkkwkl
3jW4Lcu5I9Jn8bR8pPerNO9RGEo2XmdLreGclHZ7+0QpKmUgrm6KwBYIzayuWrMH
RXqYihwhzJO2bSSGVQPd52JfK2r24x154Z/Dq/gmiw0HAGDVDYyOCAnFHfaliCLo
M1pkzLFGtXVKGDUL51JfW6r7CHH5ae1LoWLoaNAeHg/BQo57zzVF1x0Qz+Hon+cj
emBXb30EiEqWyJBBp8eIVJqcFaEpxcOmjvBAe2xFdc7HIZOY6kw=
=sVWJ
-----END PGP SIGNATURE-----

Attachment: pgpj7ivUFNI4X.pgp
Description: PGP signature


--- End Message ---

Reply via email to