# Let us know when platforms specific packages have been updated to 8.12! **URL:** \ **Category:** Distro Packagers\ **Tags:** release8-12\ **Created:** [February 10, 2024, 10:34pm UTC](https://racket.discourse.group/t/let-us-know-when-platforms-specific-packages-have-been-updated-to-8-12/2712 "2024-02-10T22:34:28Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![spdegabrielle](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/spdegabrielle/32/95_2.png) [@spdegabrielle](https://racket.discourse.group/u/spdegabrielle)\ **Post date:** [February 10, 2024, 10:34pm UTC](https://racket.discourse.group/t/let-us-know-when-platforms-specific-packages-have-been-updated-to-8-12/2712/1 "2024-02-10T22:34:28Z")
Please let us know when platforms specific packages have been updated to 8.12! The Void linux package has already been updated: [https://voidlinux.org/packages/?arch=x86\_64&q=Racket](https://voidlinux.org/packages/?arch=x86_64&q=Racket) thank you ! ---
**Author:** ![zyga](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/zyga/32/585_2.png) [@zyga](https://racket.discourse.group/u/zyga)\ **Post date:** [February 10, 2024, 11:29pm UTC](https://racket.discourse.group/t/let-us-know-when-platforms-specific-packages-have-been-updated-to-8-12/2712/2 "2024-02-10T23:29:07Z")
The snap is building now. It should go live soon. ---
**Author:** ![spdegabrielle](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/spdegabrielle/32/95_2.png) [@spdegabrielle](https://racket.discourse.group/u/spdegabrielle)\ **Post date:** [February 11, 2024, 12:11pm UTC](https://racket.discourse.group/t/let-us-know-when-platforms-specific-packages-have-been-updated-to-8-12/2712/3 "2024-02-11T12:11:20Z")
Thank oyu @zyga - I can see [https://snapcraft.io/racket](https://snapcraft.io/racket) is now 8.12 These package repositories also have Racket 8.12 available: - Docker [https://hub.docker.com/r/racket/racket/](https://hub.docker.com/r/racket/racket/) - Gentoo [https://packages.gentoo.org/packages/dev-scheme/racket](https://packages.gentoo.org/packages/dev-scheme/racket) - LiGurOS (develop) [https://gitlab.com/liguros/liguros-repo/-/tree/develop/dev-scheme/racket](https://gitlab.com/liguros/liguros-repo/-/tree/develop/dev-scheme/racket) - Termux [https://github.com/termux/termux-packages/tree/dee13f5b9/packages/racket](https://github.com/termux/termux-packages/tree/dee13f5b9/packages/racket) So thank you to the maintainers doing this work. I think it is fair to say Debian and package systems downstream from Debian (e.g. ubuntu PPA) do take longer. If you are waiting on these, please be patient, as the maintainers are all volunteers and are doing the best they can. if you don't want to wait; > The Linux build is generic enough that it should work on most distributions, including relatively old distributions. > After downloading the installer file, run it with > > `sh racket-8.12-x86_64-linux-cs.sh` > > to install, possibly adding sudo to the start of the command to install to a location that requires administrator access. Direct download: [https://download.racket-lang.org/releases/8.12/installers/racket-8.12-x86\_64-linux-cs.sh](https://download.racket-lang.org/releases/8.12/installers/racket-8.12-x86_64-linux-cs.sh) ---
**Author:** ![spdegabrielle](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/spdegabrielle/32/95_2.png) [@spdegabrielle](https://racket.discourse.group/u/spdegabrielle)\ **Post date:** [February 12, 2024, 9:00am UTC](https://racket.discourse.group/t/let-us-know-when-platforms-specific-packages-have-been-updated-to-8-12/2712/4 "2024-02-12T09:00:03Z")
Very pleased to report we have two more - Alpine Linux Edge community [https://pkgs.alpinelinux.org/packages?name=racket](https://pkgs.alpinelinux.org/packages?name=racket) - Homebrew Formulae [https://formulae.brew.sh/cask/racket](https://formulae.brew.sh/cask/racket) Thank you to the maintainers who did the work updating their repositories to include Racket 8.12 so quickly! ---
**Author:** ![jbclements](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/jbclements/32/11_2.png) [@jbclements](https://racket.discourse.group/u/jbclements)\ **Post date:** [February 19, 2024, 4:41am UTC](https://racket.discourse.group/t/let-us-know-when-platforms-specific-packages-have-been-updated-to-8-12/2712/5 "2024-02-19T04:41:44Z")
I'm checking in here on the state of racket in Ubuntu. When I search for racket PPA I wind up on Asumu's page, which hasn't been updated since 8.6, so it's now a full year out of date. At one point my understanding was that this PPA couldn't be updated until the debian upstream got updated; I think @bremner is responsible for that, and that one is now at 8.10? So I guess I have two questions: (1) Is it still the case that Asumu can't update the Ubuntu PPA until the debian version is updated? (2) Am I understanding how things work at all, or am I terribly, terribly confused? 🙂 ---
**Author:** ![bremner](https://avatars.discourse-cdn.com/v4/letter/b/aca169/32.png) [@bremner](https://racket.discourse.group/u/bremner)\ **Post date:** [February 19, 2024, 5:54pm UTC](https://racket.discourse.group/t/let-us-know-when-platforms-specific-packages-have-been-updated-to-8-12/2712/6 "2024-02-19T17:54:36Z")
John Clements via Racket Discourse [notifications@racket.discoursemail.com](mailto:notifications@racket.discoursemail.com) writes: > I'm checking in here on the state of racket in Ubuntu. When I search > for racket PPA I wind up on Asumu's page, which hasn't been updated > since 8.6, so it's now a full year out of date. At one point my > understanding was that this PPA couldn't be updated until the debian > upstream got updated; I think @bremner is responsible for that, and > that one is now at 8.10? So I guess I have two questions: (1) Is it > still the case that Asumu can't update the Ubuntu PPA until the debian > version is updated? (2) Am I understanding how things work at all, or > am I terribly, terribly confused? 🙂 Although we sometimes trade packaging code, there is no formal dependence between the Ubuntu PPA and the debian package (either way). It is correct that debian is still at 8.10. 8.11 would not build with HOME as non-existent (although that was patchable). 8.12 did not build for me out of the box either; I haven't had the time to narrow down the problem to something Debian specific or something upstream. d ---
**Author:** ![jbclements](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/jbclements/32/11_2.png) [@jbclements](https://racket.discourse.group/u/jbclements)\ **Post date:** [February 19, 2024, 6:07pm UTC](https://racket.discourse.group/t/let-us-know-when-platforms-specific-packages-have-been-updated-to-8-12/2712/7 "2024-02-19T18:07:30Z")
Thanks for the update. Let me know if there's anything I can do to help with the debian build. I'll write to Asumu separately. ---
**Author:** ![zyga](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/zyga/32/585_2.png) [@zyga](https://racket.discourse.group/u/zyga)\ **Post date:** [February 20, 2024, 6:15pm UTC](https://racket.discourse.group/t/let-us-know-when-platforms-specific-packages-have-been-updated-to-8-12/2712/8 "2024-02-20T18:15:43Z")
I've extended snap package to contain both 8.11.1 (in the channel `8.11/stable`) and 8.12 (in the channels `8.12/stable` as well as `latest/stable`). EDIT: You can see this in the drop-down in the top-right corner of [Install racket on Linux | Snap Store](https://snapcraft.io/racket) as well as in the output of `snap info racket`: ```scheme zyga@novigrad:~$ snap info racket name: racket summary: Racket Language publisher: Sam Tobin-Hochstadt (samth) store-url: https://snapcraft.io/racket contact: https://listed.zygoon.pl/ license: MIT description: | Racket is a general-purpose programming language and an ecosystem for language-oriented programming. This snap is maintained by https://listed.zygoon.pl/ and the source is available from https://gitlab.com/zygoon/racket-snap commands: - racket.drracket - racket - racket.raco - racket.slideshow snap-id: NxTKtjBiXwSfqrP5RJSArdVObhzPxuAS tracking: 8.11/stable refresh-date: today at 15:50 CET channels: latest/stable: 8.12 2024-02-11 (19) 243MB - latest/candidate: ↑ latest/beta: ↑ latest/edge: ↑ 8.12/stable: 8.12 2024-02-20 (19) 243MB - 8.12/candidate: ↑ 8.12/beta: ↑ 8.12/edge: ↑ 8.11/stable: 8.11.1 2024-02-20 (17) 243MB - 8.11/candidate: ↑ 8.11/beta: ↑ 8.11/edge: ↑ installed: 8.11.1 (17) 243MB - ``` ---
**Author:** ![bremner](https://avatars.discourse-cdn.com/v4/letter/b/aca169/32.png) [@bremner](https://racket.discourse.group/u/bremner)\ **Post date:** [March 17, 2024, 10:32pm UTC](https://racket.discourse.group/t/let-us-know-when-platforms-specific-packages-have-been-updated-to-8-12/2712/9 "2024-03-17T22:32:30Z")
John Clements via Racket Discourse [notifications@racket.discoursemail.com](mailto:notifications@racket.discoursemail.com) writes: > Thanks for the update. Let me know if there's anything I can do to > help with the debian build. I'll write to Asumu separately. There are now 8.12 packages in Debian unstable [1](https://buildd.debian.org/status/package.php?p=racket&suite=sid). There is a big transition going on in Debian right (particularly affecting 32 bit arm), so it may take a while to migrate to testing (and stable backports). I haven't heard from Asumu for a bit, but if anyone is working on packaging for Debian derivative, then I suggest looking at the updated packaging [2](https://salsa.debian.org/bremner/racket). Quite a lot has changed, and most architectures are using the CS backend now (in some cases via PB). I'm currently aware of one architecture specific bug; if someone cares about mips64el then maybe have a look at [3](https://github.com/racket/racket/issues/4952) ---
**Author:** ![LiberalArtist](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/liberalartist/32/151_2.png) [@LiberalArtist](https://racket.discourse.group/u/LiberalArtist)\ **Post date:** [March 29, 2024, 5:50am UTC](https://racket.discourse.group/t/let-us-know-when-platforms-specific-packages-have-been-updated-to-8-12/2712/10 "2024-03-29T05:50:46Z")
I've sent the patch series updating Guix to Racket 8.12: [[PATCH 0/6] gnu: Update to Racket 8.12, Chez Scheme 10, and Zuo 1.9.](https://issues.guix.gnu.org/70065) It should be merged once CI and review are done. It took a little time to update (and ultimately simplify) Guix's Chez Scheme packaging now that Racket's changes have been upstreamed. ---
**Author:** ![LiberalArtist](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/liberalartist/32/151_2.png) [@LiberalArtist](https://racket.discourse.group/u/LiberalArtist)\ **Post date:** [March 29, 2024, 6:05am UTC](https://racket.discourse.group/t/let-us-know-when-platforms-specific-packages-have-been-updated-to-8-12/2712/11 "2024-03-29T06:05:46Z")
> [@bremner](#): > > I haven't heard from Asumu for a bit, but if anyone is working on > packaging for Debian derivative, then I suggest looking at the updated > packaging [2](https://salsa.debian.org/bremner/racket). Quite a lot has changed, and most architectures are using the > CS backend now (in some cases via PB). I'm currently aware of one > architecture specific bug; if someone cares about mips64el then maybe > have a look at [3](https://github.com/racket/racket/issues/4952) Re [switch to PB backend for powerpc (b494cfd5) · Commits · David Bremner / racket · GitLab](https://salsa.debian.org/bremner/racket/-/commit/b494cfd538006e410c54d1d4e9ab8d5f202267e9), did you encounter a problem with `tppc32le` on `powerpc`? Because I think it's supposed to work. Note that, confusingly enough, in Chez Scheme machine types, the `le` suffix stands for "Linux", not "little endian" (which is `l` in `pb`-based machine types: for native machine types, endianness implied by the architecture part). (I don't have `reportbug` configured on the (Bookworm) machine where I'm writing this, but I can figure that out if you prefer.) ---
**Author:** ![bremner](https://avatars.discourse-cdn.com/v4/letter/b/aca169/32.png) [@bremner](https://racket.discourse.group/u/bremner)\ **Post date:** [March 29, 2024, 10:57am UTC](https://racket.discourse.group/t/let-us-know-when-platforms-specific-packages-have-been-updated-to-8-12/2712/12 "2024-03-29T10:57:41Z")
Philip McGrath via Racket Discourse [notifications@racket.discoursemail.com](mailto:notifications@racket.discoursemail.com) writes: > Re > [switch to PB backend for powerpc (b494cfd5) · Commits · David Bremner / racket · GitLab](https://salsa.debian.org/bremner/racket/-/commit/b494cfd538006e410c54d1d4e9ab8d5f202267e9), > did you encounter a problem with `tppc32le` on `powerpc`? Because I > think it's supposed to work. Note that, confusingly enough, in Chez > Scheme machine types, the `le` suffix stands for "Linux", not "little > endian" (which is `l` in `pb`-based machine types: for native machine > types, endianness implied by the architecture part). > > (I don't have `reportbug` configured on the (Bookworm) machine where > I'm writing this, but I can figure that out if you prefer.) Yes, the built tppc32le racket crashed when building docs. I was a bit curious if these errors are really symptoms of running out of memory during the build, but I haven't investigated further. ```scheme raco setup: 1 re-rendering: /racket-index/scribblings/main/search.scrbl raco setup: --- summary of errors --- [5:05:05] raco setup: error: during making for /compatibility-lib/mzlib raco setup: vector-length: contract violation raco setup: expected: vector? raco setup: given: # raco setup: compiling: /compatibility-lib/mzlib/string.rkt raco setup: error: during making for /data-doc/data raco setup: vector-length: contract violation raco setup: expected: vector? raco setup: given: 'break-enabled raco setup: compiling: /plot-lib/plot/private/plot3d/plot-area.rkt raco setup: error: during making for /plot-lib/plot raco setup: weak-box-value: contract violation raco setup: expected: weak-box? raco setup: given: # raco setup: compiling: /plot-lib/plot/bitmap.rkt failed in build-one in loop in module->hash ``` Full log is at [Build log for racket (8.12+dfsg1-6) on powerpc](https://buildd.debian.org/status/fetch.php?pkg=racket&arch=powerpc&ver=8.12%2Bdfsg1-6&stamp=1710911114&raw=0) ---
**Author:** ![LiberalArtist](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/liberalartist/32/151_2.png) [@LiberalArtist](https://racket.discourse.group/u/LiberalArtist)\ **Post date:** [March 30, 2024, 2:40am UTC](https://racket.discourse.group/t/let-us-know-when-platforms-specific-packages-have-been-updated-to-8-12/2712/13 "2024-03-30T02:40:39Z")
> [@bremner](#): > > ```scheme > raco setup: weak-box-value: contract violation > raco setup: expected: weak-box? > raco setup: given: # > > ``` Interesting that this error matches the one in [PB backend fails on mips64el (Debian) · Issue #4952 · racket/racket · GitHub](https://github.com/racket/racket/issues/4952). For `weak-box-value` to reject something that prints as `#` makes me suspect that some deep internal thing is going badly wrong, but what it would be is beyond me. ---
**Author:** ![mflatt](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/mflatt/32/6_2.png) [@mflatt](https://racket.discourse.group/u/mflatt)\ **Post date:** [April 8, 2024, 12:24am UTC](https://racket.discourse.group/t/let-us-know-when-platforms-specific-packages-have-been-updated-to-8-12/2712/14 "2024-04-08T00:24:44Z")
I think these failures may be due to a missing write barrier in object initialization. If one place (or OS thread generally) initializes and object and another place tries to read it, then without a write barrier, the reading thread might not yet see the tag that was written for the object. A missing barrier could explain the "box is not a box" kind of error, where the tag was not visible when it was checked, but it becomes visible by the time the error message is constructed. For tppc32le, I had never tried running on a multiprocessor, and I've been able to confirm that the object-initialization barrier was definitely missing there. A barrier would also have been missing for pb on mips64el. See also [add missing memory fences for tppc32le and pb variants by mflatt · Pull Request #825 · cisco/ChezScheme · GitHub](https://github.com/cisco/ChezScheme/pull/825). ---
**Author:** ![bremner](https://avatars.discourse-cdn.com/v4/letter/b/aca169/32.png) [@bremner](https://racket.discourse.group/u/bremner)\ **Post date:** [June 10, 2024, 12:40pm UTC](https://racket.discourse.group/t/let-us-know-when-platforms-specific-packages-have-been-updated-to-8-12/2712/15 "2024-06-10T12:40:02Z")
David Bremner [david@tethera.net](mailto:david@tethera.net) writes: > I haven't heard from Asumu for a bit, but if anyone is working on > packaging for Debian derivative, then I suggest looking at the updated > packaging [2](https://salsa.debian.org/bremner/racket). Quite a lot has changed, and most architectures are using the > CS backend now (in some cases via PB). I'm currently aware of one > architecture specific bug; if someone cares about mips64el then maybe > have a look at [3](https://github.com/racket/racket/issues/4952) Thanks to the amazing Matthew Flatt, the mipsel64el problem has been fixed in 8.13, and all Debian release architectures except armel now use the CS backend (at least in Debian unstable). If anyone is particularly interested in racket cs on Debian/armel (arm5vte) feel free to contact me. In related news, the Debian unstable packages are now updated to 8.13.