Your message dated Sat, 10 May 2025 01:20:30 +0000
with message-id <[email protected]>
and subject line Bug#1105013: fixed in racket 8.16+dfsg1-2
has caused the Debian Bug report #1105013,
regarding racket: wrong executable names on armel ('bc' suffix)
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.)


-- 
1105013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105013
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: racket
Version: 8.16+dfsg1-1
Severity: important
X-Debbugs-Cc: [email protected]

Dear Maintainer,

While looking into [an upstream discussion][1], I noticed that the 
executable names on armel are different than those on all other
architectures, because the armel names are incorrectly suffixed with 'bc':
e.g. `racketbc`, `racobc`, `drracketbc`, `scribblebc`, `plt-r6rsbc`, etc.

I believe adding `--enable-bcdefault` to the armel configure flags will
fix this issue.

Thanks as always for your superlative work on the Debian packaging of Racket!

Philip

[1]: https://racket.discourse.group/t/the-end-of-bc-downloads/3734


-- System Information:
Debian Release: 12.10
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-34-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message ---
Source: racket
Source-Version: 8.16+dfsg1-2
Done: David Bremner <[email protected]>

We believe that the bug you reported is fixed in the latest version of
racket, 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.
David Bremner <[email protected]> (supplier of updated racket 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: Sat, 10 May 2025 08:17:02 +0900
Source: racket
Architecture: source
Version: 8.16+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: David Bremner <[email protected]>
Changed-By: David Bremner <[email protected]>
Closes: 1105013
Changes:
 racket (8.16+dfsg1-2) unstable; urgency=medium
 .
   * Bug fix: "wrong executable names on armel ('bc'; suffix)",
     thanks to Philip McGrath (Closes: #1105013).
Checksums-Sha1:
 ab512005f59ce70e771842ce7c2832efdf277fad 1736 racket_8.16+dfsg1-2.dsc
 548fb3124af3331287953fa967b735ef732ac53c 26796 
racket_8.16+dfsg1-2.debian.tar.xz
Checksums-Sha256:
 34da30e85f4d7faad5e980d9ec51295a6a76372d9a7e89c28fb1910d369d8920 1736 
racket_8.16+dfsg1-2.dsc
 e895e980393a2db564d834696a6b12a558674f3f6b966bfdeeddde90b8ecfe6e 26796 
racket_8.16+dfsg1-2.debian.tar.xz
Files:
 0018896fefad8ee1770e0e2ac37ce5f8 1736 lisp optional racket_8.16+dfsg1-2.dsc
 92f05aa3ef9cabf5a27a7328cf6292d3 26796 lisp optional 
racket_8.16+dfsg1-2.debian.tar.xz

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

iHUEARYKAB0WIQS5beC2erx2PFqyC7XhcL+0NDTnAAUCaB6j8gAKCRDhcL+0NDTn
AF9zAQD35vJz8IdWKwi+EttVqWz8p5AniN65GCeBnLQDbFH7wgD/fDKAYAuxsT2f
lHJPXO3UNtCbv2QoIJwmHkJxhUobRg8=
=0R7l
-----END PGP SIGNATURE-----

Attachment: pgpLVKd31OLBf.pgp
Description: PGP signature


--- End Message ---

Reply via email to