It gets worse. This is a yum/cobbler/RedHat issue and I am having a tough time getting info from all the effected/responsible parties. Red Hat just told me "the cobbler is not provided by Red Hat so issues related to cobbler repository will not be supported." Is the local mirroring of a rhn repo part of yum or is it something cobbler added to the mix ? My impression is that it is a yum feature that cobbler exploits. “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin & Hobbes) ----- James Antill <james-yum@xxxxxxx> wrote: > Dan White <ygor@xxxxxxxxxxx> writes: > > > Red Hat Bugzilla ~ Bug 746053: yum-rhn-plugin busted: Repository rhel-x86_64-server-5 is listed more than once in the configuration > > > > Red Hat Enterprise 5.7 x86_64 kernel 2.6.18-274.3.1.el5 > > > > yum-rhn-plugin.noarch-0.5.4-22.el5_7.2 > > > > Running a cobbler-built local repository mirror for cobbler/PXE/Kickstarting > > systems. There are third party repos and a custom repo of locally required > > packages. > > > > After an update that changed me from yum-rhn-plugin-0.5.4-22.el5 to > > yum-rhn-plugin-0.5.4-22.el5_7.2, I started getting failure on any yum command > > with the message "Repository rhel-x86_64-server-5 is listed more than once in > > the configuration". > > > > I found the following workarounds: > > > > * disable yum-rhn-plugin by using "--disableplugin=rhnplugin" on the command > > line > > > > * downgrade to yum-rhn-plugin-0.5.4-22.el5 (yum-rhn-plugin-0.5.4-22.el5_7.1 has > > the same issue) and put "exclude=yum-rhn-plugin" in /etc/yum.conf > > > > It looks like an old bug crawled back into yum-rhn-plugin > > Ref: <https://access.redhat.com/kb/docs/DOC-15495> > > So ... this it the yum users list, not the developer list. And the > yum developers are far from experts on yum-rhn-plugin. So you might > get more ideas/help if you talk to the RHN developers. > However I do know that recent versions of the RHN plugin would cache > the list of channels the system was subscribed to ... so that might be > the problem. > > > -------------- > > > > Second question: Is there a way to do the equivalent of a yum-versionlock at the repository ? > > I'm not sure what you mean ... if you mean apply versionlock > semantics (basically version specific excludes) to just a single > repo. ... then there's no user way to do that atm. ... but the APIs > would allow it. > > -- > James Antill -- james@xxxxxxx > _______________________________________________ > Yum mailing list > Yum@xxxxxxxxxxxxxxxxx > http://lists.baseurl.org/mailman/listinfo/yum _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxx http://lists.baseurl.org/mailman/listinfo/yum
