Elliot Saba

It doesn’t actually work to just call revise(mod), that doesn’t force re-reading of the source on disk.

[noblock] It's not so easy: https://buildkite.com/julialang/yggdrasil/builds/8277#018d8ac9-3c6f-42aa-9668-e945d5931a7f

That seems quite drastic, why not just resolve the conflicts here?

I'm having the same issue, but on aarch64. I've run the updater multiple times, and it always crashes like this.

One point of contention here; the `Pkg.Types.stdlibs()` function seems to be [used in the ecosystem](https://juliahub.com/ui/Search?q=Pkg.Types.stdlibs()&type=code), but I like the `StdlibInfo` struct a lot more than just a random tuple. Should...

@KristofferC If you are happy with this, I will make a breaking `v2.0.0` release of HistoricalStdlibVersions, register that, then drop the commit here that manually installs that branch. (Kudos on...

> Just to double-check: the Pkg.Types.stdlibs() function is not currently public, right? So in theory we are allowed to make whatever breaking changes we want? Yes, and perhaps the _right_...

Alright, I'm happy with this, the new HSG version has been published and as long as @KristofferC's happy with it, I think we're good to merge.

I'm a little against doing this kind of processing on the server-side. We would need to decompress, extract, recompress and transmit the piece of the data that you're asking for,...

If it's just a private server, I think I would instead just create a second service that gets registries from an upstream package server, and does whatever this application requires....