fix: metadata_expire for whitewaterfoundry repos is too short #230
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
metadata_expire was set to 300 (seconds?), which meant long waits in each dnf command, for a repo that rarely changes. this fix the value to 30d, assuming that this was the original intent.
|
Hello @tsvikas , Thank you for the contribution. I'll talk with the wslu maintainer because now this is managed as a COPR one. So we can change the value there. Regards, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The value of
metadata_expirewas previously set to 300 (seconds?), which meant the cache was always expiring, and eachdnfcommand had long waits, for a repo that rarely changes, and doesn't have proxies.This PR sets the value to 30d, assuming that this was the original intent.
(unless it was 300d? i assume it's also possible)