yum is needed by package yum

Guillaume Dargaud wrote:
> Hello all,
> I can't update anything on the system because of the following:
> $ sudo yum update yum
> Loading "rhnplugin" plugin
> Loading "kernel-module" plugin
> This system is not registered with RHN.
> RHN support will be disabled.
>
> [snip]
>
> Error: Missing Dependency: yum = 3.2.8-1.sl is needed by package
> yum-updatesd
>
> [snip]

1. If you're updating from some repository other than RHN (because you
have no RHN support), you can uninstall yum-rhn-plugin. I believe only
genuine Red Hat supplies the rhn packages, so I'll reiterate the
question of *why* you've been updating genuine RH from the SL repo. Is
SL really that shady on purpose or did you just get mixed up?

2. The error isn't that yum needs yum. The error is that your current
version of yum-updatesd needs your current version of yum. Either
uninstall yum-updatesd (because you're probably not using that, either)
or update it simultaneously with yum.

> 1. If you're updating from some repository other than RHN (because you
> have no RHN support), you can uninstall yum-rhn-plugin. I believe only
> genuine Red Hat supplies the rhn packages, so I'll reiterate the question
> of *why* you've been updating genuine RH from the SL repo. Is SL really
> that shady on purpose or did you just get mixed up?


You are right that this is the default behavior so the distro must be brain
dead.
I don't have much choice in the distro (for both professional and technical
reasons).
I thought there'd be some equivalent repositories for SL5, but I can't find
them (https://www.scientificlinux.org/community/repo)
So is it possible to obtain RHN support/license ?

> 2. The error isn't that yum needs yum. The error is that your current
> version of yum-updatesd needs your current version of yum. Either
> uninstall yum-updatesd (because you're probably not using that, either) or
> update it simultaneously with yum.

"yum remove yum-updatesd" apparently wants to remove yum and pirut, so I'll
pass for now !
--
Guillaume Dargaud
http://www.gdargaud.net/

Guillaume Dargaud wrote:
>> 1. If you're updating from some repository other than RHN (because you
>> have no RHN support), you can uninstall yum-rhn-plugin. I believe only
>> genuine Red Hat supplies the rhn packages, so I'll reiterate the question
>> of *why* you've been updating genuine RH from the SL repo. Is SL really
>> that shady on purpose or did you just get mixed up?
>
It may not be that bad. Perhaps you can remove the link to RHN from your
/etc/yum.repos.d directory and see if there is a file called something like
rhel.repo. If so, get it out of there (do not delete it: you may regret it
and wish to put it back). In my distro, it is not there (they must have some
other way to get that one) but some others are.
>
> You are right that this is the default behavior so the distro must be brain
> dead.

I do not know that it is brain dead. It may just be a slight configuration
error, but I have never investigated how Red Hat do this. And your distro
may be different.

I just looked at CentOS 4 that is running on my other machine, and
/etc/yum.repos.d contains:

[/etc/yum.repos.d]$ ls -l
total 8
-rw-r--r-- 1 root root 2490 Jul 26 2008 CentOS-Base.repo
-rw-r--r-- 1 root root 610 Jul 26 2008 CentOS-Media.repo

Check your /etc/yum.repos.d directory and see if you can understand how it
works.

> I don't have much choice in the distro (for both professional and technical
> reasons).
> I thought there'd be some equivalent repositories for SL5, but I can't find
> them (https://www.scientificlinux.org/community/repo)
> So is it possible to obtain RHN support/license ?

You could get a support license from Red Hat for about $350/year for their
cheapest, most basic option. This would allow you to run Red Hat Enterprise
Linux at no additional charge. And pick up future releases of RHEL as well,
at no additional charge.

But if your current distribution is not RHEL, but SL5 (that I know nothing
about), I would worry about doing this unless you propose to switch to RHEL
at the same time. You might get into horrible RPM dependency problems if the
versions of all the pieces are not compatible.


--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 07:40:01 up 21 days, 18:29, 3 users, load average: 4.13, 4.19, 4.16

Guillaume Dargaud wrote:
>> 1. If you're updating from some repository other than RHN (because you
>> have no RHN support), you can uninstall yum-rhn-plugin. I believe only
>> genuine Red Hat supplies the rhn packages, so I'll reiterate the question
>> of *why* you've been updating genuine RH from the SL repo. Is SL really
>> that shady on purpose or did you just get mixed up?
>
>
> You are right that this is the default behavior so the distro must be brain
> dead.
> I don't have much choice in the distro (for both professional and technical
> reasons).
> I thought there'd be some equivalent repositories for SL5, but I can't find
> them (https://www.scientificlinux.org/community/repo)
> So is it possible to obtain RHN support/license ?

Starting from the source you quote, I get:
ftp://ftp.linux-ink.ru/pub/SL/

>> 2. The error isn't that yum needs yum. The error is that your current
>> version of yum-updatesd needs your current version of yum. Either
>> uninstall yum-updatesd (because you're probably not using that, either) or
>> update it simultaneously with yum.
>
> "yum remove yum-updatesd" apparently wants to remove yum and pirut, so I'll
> pass for now !

You should still be able to uninstall yum-rhn-plugin.
You should still be able to update yum and yum-updatesd simultaneously.

On Jul 9, 11:57 am, Guillaume Dargaud <N....DeleteThis@in2p3.fr> wrote:
> Hello all,
> I can't update anything on the system because of the following:
> $ sudo yum update yum
> Loading "rhnplugin" plugin
> Loading "kernel-module" plugin
> This system is not registered with RHN.
> RHN support will be disabled.
> Setting up Update Process
> Resolving Dependencies
> --> Running transaction check
> --> Processing Dependency: yum = 3.2.8-1.sl for package: yum-updatesd
> ---> Package yum.noarch 0:3.2.19-25.sl set to be updated
> --> Finished Dependency Resolution
> Beginning Kernel Module Plugin
> Finished Kernel Module Plugin
> Error: Missing Dependency: yum = 3.2.8-1.sl is needed by package
> yum-updatesd
>
> $ rpm -qa | grep yum
> yum-conf-51-1.SL.noarch
> yum-rhn-plugin-0.5.3-12.el5_2.9.noarch
> yum-3.2.8-1.sl.noarch
> yum-metadata-parser-1.1.2-1.sl5.i386
> yum-updatesd-3.2.8-1.sl.noarch
>
> $ uname -a
> Linux lpsc6185x.in2p3.fr 2.6.18-128.1.1.el5PAE #1 SMP Tue Feb 10 12:05:11
> EST 2009 i686 i686 i386 GNU/Linux
>
> Any help ?
> I found a few references to this problem on the net, but they didn't help..
> Thanks

Rip yum-rhn-plugin and yum-updatesd ithe hell out if if you are using
local yum repositories, rather than calling back to the mothership.
Registering with the RHEL mothership is useful: it gets you notices of
security updates, and sitewide update management with yum-updatesd.
But yum-rhn-plugin is *NOT* a normal yum utility: it is "up2date"
dressed in grandmother's clothing, waiting to ignore yum directives
and replace your locally modified packages with RedHat's officially
provided ones, and it is *nasty* if you work with RPMforge or EPEL
packages or modify your kernels to support NTFS.

I approve of registration, so people pay their license fees and reward
RedHat for their hard work. But if you have a broad kickstart
deployment policy, or install Beowulf clusters or virtual machines and
don't want to individualize the machines even if you have enough
licenses, set up one machine with a license and use the 'reposync'
tool to download all the packages to a local HTTP repository, run
'createrepo' on it, and point your local machines to that much more
manageable yum repository.