Your message dated Sun, 13 Sep 2026 15:21:50 +0200
with message-id <[email protected]>
and subject line Re: Bug#1147587: Manual buildd bootstrap request / seeding:
mit-scheme (12.1-6) on [arm64, i386, ppc64el]
has caused the Debian Bug report #1147587,
regarding Manual buildd bootstrap request / seeding: mit-scheme (12.1-6) on
[arm64, i386, 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.)
--
1147587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1147587
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: buildd.debian.org
Severity: normal
X-Debbugs-CC: [email protected], [email protected]
Dear Buildd Admins and Porters,
I have uploaded mit-scheme 12.1-6 targeting amd64, arm64, i386, ppc64el.
Because mit-scheme is a self-hosting compiler, it requires a working
/usr/bin/mit-scheme in the build environment. In 12.1-6 there are two
binary packages that supply this: mit-scheme (native code
implementation) and mit-scheme-svm (slower bytecode-based
implementation). Either will satisfy the build dependency.
Because of this circularity, the autobuilders on [arm64, i386,
ppc64el] are currently BD-Uninstallable.
To break this bootstrap cycle, could you please perform a manual
seeding step on these buildds? Appropriate binary .deb files were
uploaded, namely:
- mit-scheme_12.1-6_arm64.deb
- mit-scheme-svm_12.1-6_i386.deb
- mit-scheme-svm_12.1-6_ppc64el.deb
Package Details:
- Source Package: mit-scheme
- Version: 12.1-6
- Affected Architectures: arm64, i386, ppc64el
- Logs/Status: https://buildd.debian.org/status/package.php?p=mit-scheme
Please let me know if you need me to supply any information or files
out-of-band to facilitate this.
Cheers,
--Barak.
--- End Message ---
--- Begin Message ---
On 2026-09-13 13:53, Barak A. Pearlmutter wrote:
> > These packages are not in the archive. I guess they went through the NEW
> > queue and got thrown away [1]. As a first step you should try to
> > reupload those binaries.
>
> Done.
>
> (I did use porterboxes to generate these, of course. After qemu was
> just too darn slow!)
And the buildd.d.o page indeed show them as installed. You will probably
want to ask the release team to schedule binNMUs to allow the migration
to testing, unless you plan to do another source-only upload.
Anyway from the wb-team point of view the problem is solved, closing the
bug.
Regards
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
[email protected] http://aurel32.net
--- End Message ---
