Re: mergerepo weird behavior
seth vidal <[email protected]> Tue, 16 Aug 2011 15:12:30 -0400
| Newsgroups | gmane.linux.rpm.metadata |
|---|---|
| Message-ID | <1313521950.20287.81.camel@oliver> |
On Tue, 2011-08-16 at 10:17 -0400, Jon Wallace wrote:
> Hello,
>
> I sent some file contents a few days ago to show the results I was
> getting in reference to sequential merges of repositories in different
> combinations. I haven't heard back from anyone on this...just curious
> if I should open a ticket on it, if everyone is just busy, or if this
> just wasn't found to be an interesting problem. Not sure of protocol, I
> guess is my question here. I usually try to find out if something is a
> known issue before submitting a bug ticket. Any constructive
> suggestions? Should I submit a fix for review or is there a fixed set
> of developers working on createrepo?
1. F11 is quite old
2. the createrepo in there has seen a fair number of changes, too.
3. Can you verify in createrepo/merge.py in your createrepo pkg that you
see something that says:
metadata_expire=0,
anywhere in there?
I doubt it is - it was added in jan of 2011.
Seems likely that a newer createrepo will solve your problem.
-sv