Earlier quoted context omitted.
I did not know package managers relied on Github, this is the most unwise thing to do from a package manager perspective. Anyone could just change username/organization and break thousands/millions of build.
> Anyone could just change username/organization and break thousands/millions of build. GitHub redirects you to the new name in the event of a rename and you look up the old one.
GitHub Packages Is Down
21–30 of 83 posts
Re: GitHub Packages Is Down
#22FYI: this breaks homebrew
Nix too I presume
The binary hosting at https://cache.nixos.org/ is independent of GitHub, and so are the old-style channels at https://channels.nixos.org/. The new-style flake registry used to be fetched from GitHub but has now been moved to https://channels.nixos.org/flake-registry.json. Admittedly in a new-style situation you’re likely to be using unlocked flake references that refer to GitHub (e.g. Nixpkgs), but it’s on you to lock them and pull them into your Nix store in that case.
Of course, you also get GitHub references for upstreams that host their code there, but that applies to almost any distro(’s build system) except the oldest of the old-timers which host the source for the whole distro on their own infrastructure, like Debian. (I happen think the old-timers are right here, but that’s beside the point.)
Re: GitHub Packages Is Down
#23Earlier quoted context omitted.
I think it will break any of the open source package managers that rely on GitHub's proprietary hosting and distribution. Cargo, etc.
no, this is GitHub packages , not GitHub repositories. Cargo doesn't use this. It doesn't use GitHub repositories either, they store the crates internally. EDIT: I was wrong, the crates index does use a GitHub repo
crates.io also uses GitHub as an OAuth provider (and it's currently the only one offered), so if that broke then people wouldn't be able to publish crates, though downloading existing ones would presumably still work since you don't have to log in to do that.
Re: GitHub Packages Is Down
#24The "is" seems to be used confusingly here. This reads better as either: * GitHub's Packages Service is down * GitHub Packages are down
The name is GitHub Packages. It's singular. The use of "is" is correct here. GitHub uses "is" in similar circumstances as well.
Re: GitHub Packages Is Down
#25Earlier quoted context omitted.
I think it will break any of the open source package managers that rely on GitHub's proprietary hosting and distribution. Cargo, etc.
no, this is GitHub packages , not GitHub repositories. Cargo doesn't use this. It doesn't use GitHub repositories either, they store the crates internally. EDIT: I was wrong, the crates index does use a GitHub repo
[1] https://github.com/rust-lang/cargo/blob/master/src/cargo/sou...
Re: GitHub Packages Is Down
#26Earlier quoted context omitted.
no, this is GitHub packages , not GitHub repositories. Cargo doesn't use this. It doesn't use GitHub repositories either, they store the crates internally. EDIT: I was wrong, the crates index does use a GitHub repo
Cargo is hard-coded to use GitHub for the crates.io index [1] [1] https://github.com/rust-lang/cargo/blob/master/src/cargo/sou...
Re: GitHub Packages Is Down
#27Earlier quoted context omitted.
I did not know package managers relied on Github, this is the most unwise thing to do from a package manager perspective. Anyone could just change username/organization and break thousands/millions of build.
> Anyone could just change username/organization and break thousands/millions of build. GitHub redirects you to the new name in the event of a rename and you look up the old one.
Re: GitHub Packages Is Down
#28Earlier quoted context omitted.
Does it break all of Homebrew or just some packages? I never knew homebrew started using GitHub Packages.
Homebrew uses it to store bottles (the built assets).
Re: GitHub Packages Is Down
#29[flagged]
Notwithstanding that services on third party systems are a weird reason to buck a first party platform.
Re: GitHub Packages Is Down
#30Earlier quoted context omitted.
no, this is GitHub packages , not GitHub repositories. Cargo doesn't use this. It doesn't use GitHub repositories either, they store the crates internally. EDIT: I was wrong, the crates index does use a GitHub repo
Cargo is hard-coded to use GitHub for the crates.io index [1] [1] https://github.com/rust-lang/cargo/blob/master/src/cargo/sou...