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
Yum repodata becomes stale pretty quickly #2816
Comments
Thanks @BrandonIngalls. Cc: @oconnor663 |
Wow, thanks for the detailed fixes. If all we need to do is avoid deleting the old package files from S3, I think this should be a trivial change to our push script. I'll set aside some time to test it and make sure nothing breaks. |
Clients with cached repo data might try to fetch older binaries, and we prefer to let them do that rather than giving them nasty errors. They should eventually get the latest stuff when they run the equivalent of `apt-get update`. Fixes keybase/keybase-issues#2816.
This change should go out with tomorrow's build, though it won't automatically apply to your machine unless you delete |
Keybase frequently causes my workstation to fail updating as the package your repo says is available seems to disappear whenever a newer version is pushed out.
[~]$ sudo dnf update ... [MIRROR] keybase-1.0.18.20170206170059.4931777-1.x86_64.rpm: Status code: 404 for http://prerelease.keybase.io/rpm/x86_64/keybase-1.0.18.20170206170059.4931777-1.x86_64.rpm [FAILED] keybase-1.0.18.20170206170059.4931777-1.x86_64.rpm: No more mirrors to try - All mirrors were already tried without success ... Error: Error downloading packages: Cannot download keybase-1.0.18.20170206170059.4931777-1.x86_64.rpm: All mirrors were tried
Attempting to download the file that is in my computers cached data about the keybase repo.
Two possible solutions:
I understand wanting people to have the latest version, but that shouldn't come with the risk of breaking automated system events -- even if you are only breaking them for hours / days.
The text was updated successfully, but these errors were encountered: