> I think you are running into the same yum RHN issue I hit a few days
> ago. Basically yum + yum-metadata-parser from 5.2 appear to have
> a bug when pulling dependency information via RHN repos.
>
> The following is a snippet of yum debug output when talking to
> identical repositories, the first via RHN the second straight http.
> < looking for ('tcl-devel', 'EQ', ('0', '8.4.13', '0')) as a requirement of
> tk-devel.x86_64 0-8.4.13-5.el5_1.1 - u
> > looking for ('tcl-devel', 'EQ', ('0', '8.4.13', None)) as a requirement of
> > tk-devel.x86_64 0-8.4.13-5.el5_1.1 - u
>
> When talking to RHN, the release version in a Requires is forced
> to 0 if it does not exist. What seems to be the proper operation
> is seen when not talking through yum-rhn-plugin.
>
> Reverting to the 5.1 version of yum and yum-metadata-parser (3.0.1
> and 1.0-8) is functional as a temporarily workaround.
>
> I had not filed a bug report yet since I have not had time to
> validate the issue by digging into the code and/or replicating with
> clean installs against a second RHN server. If you beat me to it,
> please forward along the BZ/IssueTracker number.
Interesting. Well, unfortunately I can no longer reproduce this. We
upgraded our satellite server last night to 5.0.2 and I've sync'd it
twice since then, so perhaps the metadata got refreshed or kicked
somehow so it's now correct.
In any case, yum this morning on the same machine isn't complaining and
did the update correctly.
Thanks
Ray
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
