New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mariadb: provide multiple src url mirrors #41871
Conversation
@GrahamcOfBorg build mariadb mariadb.connector-c |
Success on aarch64-linux (full log) Attempted: mariadb, mariadb.connector-c Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: mariadb, mariadb.connector-c Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: mariadb Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: mariadb Partial log (click to expand)
|
1c751d2
to
79e9a22
Compare
Success on x86_64-linux (full log) Attempted: mariadb Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: mariadb Partial log (click to expand)
|
Are the mirrors particular unstable that we need them? |
I don't see why this is necessary for a single package unless the standard download site fails really often. After all the source is only downloaded once and then cached until the hash changes... Also there's a trust issue with non-official mirrors because of the "trust on first use" process most people use for updating source hashes. |
I had a few hours where I wasn't able to access mariadb.org, but could access mariadb.com -- they both appear accessible now, though. On the connector-c one, I happen to have some machines on a corporate network that doesn't allow FTP traffic from untrusted sites, because the connect-back port gets blocked. The mirrors appear to be stable, but if we want to just have 1 of them it'd be nice to pick an HTTPS mirror instead of FTP/SSH. Same issue as in #41761 and #41774 I was using an overlay for a bit that used the digitalocean mirror (https://downloads.mariadb.org/interstitial/connector-c-2.3.6/mariadb-connector-c-2.3.6-src.tar.gz/from/http%3A//mirror.nodesdirect.com/mariadb/?serve), but I noticed it was down several times, which is why I added 3 of them. It's a little awkward because of the long, version-specific prefix, so it doesn't fit well into FWIW while these are third-party mirrors, they're listed on the official download site: |
Having both mariadb.org/mariadb.com should be fine. For the other mirrors switching from ftp to https sounds also like a good idea. |
Ok, should we merge this as-is, or would you like me to delete some of the connector-c mirrors and just leave 1 HTTPS one? |
Both mariadb.com and mariadb.org appear to be canonical upstream sources, and have identical sha256 hashes at these URLs. For the third-party mirrors, if we are just going to provide one URL, it should be an HTTPS url instead of FTP or SSH, which many users may not be able to access due to network security configurations.
79e9a22
to
3bb3055
Compare
Ok, I left the mariadb.com and mariadb.org mirrors, but for connector-c I've swapped it to rely on just one HTTPS mirror from the list of official mirrors. Also rebased to fix merge conflicts with a connector-c update. |
@GrahamcOfBorg build mariadb mariadb.connector-c |
Success on x86_64-linux (full log) Attempted: mariadb, mariadb.connector-c Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: mariadb, mariadb.connector-c Partial log (click to expand)
|
@xeji this is true for anyone using the hydra binary cache, but it's not true for users who aren't -- either because they have a non-root installation in a non-standard store path, or they prefer to build from source to avoid trusting third-party binaries. For these users, fragile source urls are somewhat of an annoyance, because they more frequently rely on them. It looks like the content-addressed tarballs.nixos.org mirror doesn't automatically mirror source tarballs as they're added, since they're often missing. I see some maintainers perl scripts for mirroring, so I assume it's a manual process? At any rate, when upstream gives us N equivalent mirror sites, it's somewhat nice to allow swapping between them, as we do in mirrors.nix. If nothing else, preferring an HTTPS one over FTP when possible is nice :) |
Success on x86_64-linux (full log) Attempted: mariadb Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: mariadb Partial log (click to expand)
|
Sorry, I don't know. |
Thanks @xeji! |
Both mariadb.com and mariadb.org appear to be canonical upstream sources, and
have identical sha256 hashes at these URLs.
For the third-party mirrors, we should provide multiple for better availability,
and also note that some users may not be able to process FTP traffic due to
network security settings.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)