JuliaStats/StatsModels package missing?

I can’t install StatsModels in julia 1.1; when I try Pkg.add(“StatsModels”) it asks me for a github login, and no matter what I put in it fails. Looking at github for JuliaStats/StatsModels.jl, I get a 404 error, although google has a cache of the old github page. Am I misconfiguring something somehow?

google cache of old github.com/JuliaStats/StatsModels.jl: https://webcache.googleusercontent.com/search?q=cache:YAAzS4B_a3MJ:https://github.com/JuliaStats/StatsModels.jl+&cd=1&hl=en&ct=clnk&gl=us&client=firefox-b-1-d

The repository has been deleted by mistake. JuliaStats people already asked GitHub to restore it, waiting for GitHub :crossed_fingers:

2 Likes

Ah, great, thanks for the update. Good to know when thing go wrong it’s not always my own fault.

Just a quick note here (which is also a bit of a plug). JuliaPro and JuliaTeam users are not affected by this. Basically, JuliaPro users are pulling packages from a JuliaTeam server run by Julia Computing. JuliaTeam users have their own in-house package server. In both cases, they are not pulling from the upstream repo directly.

In fact, Stefan articulated the need for backups in the JuliaTeam vision blog. We probably want the default Julia Pkg to also stop pulling packages directly from package repos. Doing so will prevent such issues, while also giving authors much needed package usage stats, and allow authors to develop packages anywhere (not necessarily only github).

-viral

2 Likes

Wow, how it was deleted by mistake? Someone must have typed the repository name letter-by-letter for GitHub to accept the deletion, correct?

2 Likes

There is already a (unofficial) mirror in place: [ANN] UnofficialJuliaMirror: Mirror of all registered Julia packages

I guess this is causing my Travis to stall for 10 minutes, which has given me some misery over the past 2 hours:

Cloning [3eaba693-59b7-5ba5-a881-562e759f1c8d] StatsModels from https://github.com/JuliaStats/StatsModels.jl.git
Username for 'https://github.com': 

Yes. I also got at that point trying to update my packages. I fear that many people will experience issues related to this even though they’re not installing the package

The repo had been accidentally deleted (instead of deleting a fork), but GitHub has now restored it so everything should be fine again. This indeed illustrates the usefulness of having a mirror in the future.

1 Like