Skip to content
This repository has been archived by the owner on May 9, 2022. It is now read-only.

Caches aren't invalidated if you switch instrepo / version #32

Open
wgwoods opened this issue Nov 1, 2013 · 1 comment
Open

Caches aren't invalidated if you switch instrepo / version #32

wgwoods opened this issue Nov 1, 2013 · 1 comment
Labels
Milestone

Comments

@wgwoods
Copy link
Contributor

wgwoods commented Nov 1, 2013

If you do something like fedup --network 19, and then decide, whoops, I want to go to 20, we'll still use the cached metadata from the Fedora 19 versions of all the repos.

We need to invalidate the cached metadata whenever the user changes the version or the URL of --instrepo.

@wgwoods wgwoods modified the milestones: 0.9.0, disk handling Oct 13, 2014
@wgwoods
Copy link
Contributor Author

wgwoods commented Oct 24, 2014

We could probably fix most of this by using the default yum metadata dir for our repos. This would also mean that the system doesn't need to redownload the new repodata after the upgrade, which would be kind of helpful.

--instrepo is a little different, but saving and examining the fedup arguments also relates to #51, where we'd want to save sys.argv or the args object so we can implement fedup --continue..

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant