Description of problem:
I've hit this one while trying to update to a new zif build I pushed into my own repo. I KNOW there's a new build waiting in the repo, but KPackageKit won't show it to me, even after I explicitly ask it to refresh the available updates.
Version-Release number of selected component (if applicable):
Always (when the metadata has changed without having expired).
Steps to Reproduce:
1. Try to refresh the list of available updates in KPackageKit.
The new updates get detected.
I noticed the code does nothing at all when "force" is not set (is that correct? I'd expect it to refresh the expired metadata in that case), and does nothing to ignore the expiration date when "force" is set (whereas PackageKit-yum does a repo.metadata_expire = 0 in refresh_cache; BTW, it does that always, unconditionally, even without "force", so it's no wonder we're seeing excessive refreshes with PackageKit-yum).
I filed bug #740018 against PackageKit-yum, because the code there really doesn't look right to me.
Uhm, actually that's probably not what's happening, I'm hitting some error inside zif itself, it's failing to load the metadata for my repo, I have to check what's going on.
Yes, it was my repodata which was corrupt (outdated repomd.xml left on the server), so my "I KNOW there's a new build waiting in the repo" assertion was where the PEBKAC was. Sorry for the bogus bug report.
(In reply to comment #3)
> Yes, it was my repodata which was corrupt (outdated repomd.xml left on the
> server), so my "I KNOW there's a new build waiting in the repo" assertion was
> where the PEBKAC was. Sorry for the bogus bug report.
Dude, don't worry. I appreciate all the other bugs.