alpha dnf/yum repo could use metadata_expire=1
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I'm using the alpha version where we get updates about once a day or so, if I simply run
sudo dnf upgrade keybase
like the popup suggests, dnf sometimes tells me there is nothing to do.
but today I edited
sudo vi /etc/yum.repos.d/keybase.repo
and added
metadata_expire=1
and now every call to
sudo dnf upgrade keybase
first gets the latest metadata and then tries to upgrade.
Would it make sense for the keybase installer to set this flag automatically?
This is tested on Fedora 23
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating how the installer creates the Fedora repository file at /etc/yum.repos.d/keybase.repo. Check the existing alpha repository settings and determine whether metadata_expire=1 should be applied automatically. Done means the generated repository configuration refreshes metadata before the suggested dnf upgrade on Fedora.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fedora, linux
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100