@massung If you need the same kind of path setup for others things, it’s worth to know about /etc/paths.d/ . See https://golangbyexample.com/understand-etc-paths-pathsd-mac/
But doesn’t that affect all users (assuming there might be more than one human, though that is a rarity these days)?
It does, but, not a problem in my case (as you noted)
I know this thread is old, but why are people (beginners?) writing macros with #lang racket/base instead of #lang racket?
More master/main headaches… This is on a fresh install of 8.2 CS on Windows, doesn’t happen on my macOS install. Is this a problem with my package config on the package server, the package server itself, or with Racket, or with git on my Windows machine (using 2.32.0)? PS C:\Users\Joel> raco pkg install beeswax
Resolving "beeswax" via <https://download.racket-lang.org/releases/8.2/catalog/>
Resolving "beeswax" via <https://pkgs.racket-lang.org>
Downloading repository <https://github.com/otherjoel/beeswax.git#main>
git: could not find requested reference
reference: master
repo: otherjoel/beeswax.git
context...:
C:\Program Files\Racket\collects\net\git-checkout.rkt:403:0: select-commits
...
Looks like a bug in raco pkg but it seems odd, that only Windows is affected. It’s worth trying an raco setup but I don’t have an idea for where to look for the problem.
I see that raco pkg install "<https://github.com/otherjoel/beeswax.git#main>" works on my machine (Mac OS), but not raco pkg install beeswax. Confusingly, I bet it starts works in a little while..
The problem is that raco pkg install beeswax gets a commit ID from the pkg server, which it sends on to git-checkout . Using the full URL with raco pkg install passes the branch main to git-checkout.
I already have the “Branch or commit” field for the package set to main on the package server though?
So why does git-checkout get confused by a commit ID, which is more specific? I forget exactly why, but git-checkout over the revelant protocol can’t ask for a specific commit, or something like that. It can ask for branches or tags. Given a commit ID, it has to find it in a branch.
Currently, it’s just looking from master , and it doesn’t find the commit that way.
When the package server catches up to your branch’s new commit, then git-checkout will see the commit ID associated with main, and things will work again.
Long story short: Yes, a bug in raco pkg, which probably hadn’t been pinned down before because the bad state turns out to be ephemeral in practice.
Ah I see.
#lang racket imports a lot of stuff compared to #lang racket/base
I guess it’s actually a bug in git-checkout, which is supposed to fall back to checking all branches and tags. But it doesn’t expect failure trying just “master”. (Also, it would be better to check just “main”, first.)
I installed beeswax a few weeks ago on my mac (8.0 CS) with no trouble, if that helps nail things down.
Yeah the bug is apparently surfacing because I just pushed an update to the repo this morning and the package server hasn’t caught up yet.
Repair pushed (for client versions after v8.2, of course)
Thanks! and the package server is working again by this point, as you predicted.
Encountering the same problem with sawzall that @hazel just pushed some changes to. Thanks for fixing Matthew.