Some of our users are getting 404's when downloading prestodelta.xml. I suspect it's because the users have an (outdated) cached copy of repomd.xml. prestodelta.xml doesn't get downloaded until install time, which means it won't be in the cache. Seth, how do you deal with this for filelists.sqlite and other.sqlite? Is there any way for yum-presto to tell yum to invalidate the cache if it gets a 404? Is that even a good idea? Any suggestions?
by the time presto data is grabbed it's a bit late to invalidate the metadata, I would think. And I'm confused how the metadata is current enough for the pkgs to be downloaded but not for the presto data? it should be the same, I would think.
(In reply to comment #1) > by the time presto data is grabbed it's a bit late to invalidate the metadata, > I would think. Fair enough. > And I'm confused how the metadata is current enough for the pkgs to be > downloaded but not for the presto data? it should be the same, I would think. After a new push, most of the packages haven't changed, so the old metadata is mostly right. For the few cases it's wrong that a user would notice (as far as I can see, it would have to be a package updated twice in two sequential pushes), you would get 404's for the missing packages. prestodelta's name changes after *every* push, so you get a 404 every time you use the old metadata. I do want to point out that I've only seen two people complaining about this on IRC, and a 'yum clean metadata' fixed it for them. It may be that we're better off doing nothing here.
I think it's odd that things are not timing out properly but unless it starts happening all over we should probably wait it out.
Ok, going to close as WONTFIX; if we run into problems, we'll reopen.