Red Hat Bugzilla – Bug 787186
Two repoquery runs with same repoid but different repositories uses first one
Last modified: 2014-01-21 18:20:50 EST
Created attachment 559284 [details]
Two sample repositories
Description of problem:
Two consecutive repoquery runs with same repoid, firstly with newer repository timestamp, secondly with older repository timestamp shows warning and uses data from first one.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Download & unpack attached repositories into cwd.
repoquery -a --repoid=foobar --repofrompath=foobar,file://`pwd`/repo1
repoquery -a --repoid=foobar --repofrompath=foobar,file://`pwd`/repo2
Not using downloaded repomd.xml because it is older than what we have:
Current : Fri Feb 3 13:36:43 2012
Downloaded: Fri Feb 3 13:36:33 2012
Print without warning:
Repository is cached in
you might want to delete it before next run.
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" and open it against that version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.