For packages I do not have "yum info foo" will tell me what repo provides
it. But for the ones that I already have installed it just gives a
useless "installed" epithet.
[good]
Name : zope
Arch : i386
Version: 2.10.7
Release: 1.el5
Size : 14 M
Repo : epel
vs
[useless]
Name : authconfig-gtk
Arch : i386
Version: 5.3.21
Release: 3.el5
Size : 188 k
Repo : installed
In case you wonder why I need it: I have been getting this error under
yum last few days:
///////////////////////
There was an error communicating with RHN.
RHN support will be disabled.
Error Message:
Service not enabled for system profile: "polaris"
Error Class Code: 31
Error Class Info:
This system does not have a valid entitlement for Red Hat Network.
Please visit
https://rhn.redhat.com/rhn/systems/SystemEntitlements.do
or login at https://rhn.redhat.com, and from the "Your RHN" tab,
select "Subscription Management" to enable RHN service for this
system.
//////////////////////////
We used to have RHEL a while ago but then we moved to Fedora. I'm not
sure why this error started popping now (well I do have a suspicion; I
think I had a runaway script run yum too many times and got blacklisted
by them! )
I guess I need to remove all refs to the offending repo to make this
error message dissapear. Before doing that I was planning to run an eye
over my installed list of packages to make sure we do not have any from
the RHEL repo still.
Of course, feel free to let me know if my strategy is stupid (often is!)
or I am barking up the wrong tree!
"yum repolist" produces
epel Extra Packages for Enterprise Linux 5 - enabled
--
Rahul
epel should not be a problem (I use epel with my CentOS 4 systems).
What does a directory listing of /etc/yum.repos.d yield? Do you have a
RHN repo listed there?
>
--
Robert Heller -- 978-544-6933
Deepwoods Software -- Download the Model Railroad System
http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows
hel...@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
> epel should not be a problem (I use epel with my CentOS 4 systems).
>
> What does a directory listing of /etc/yum.repos.d yield? Do you have a
> RHN repo listed there?
>
Thanks Robert!
\ls /etc/yum.repos.d
epel.repo epel-testing.repo rhel-debuginfo.repo
But this was always listed for the last year. I did not change it. I'm not
sure what went wrong.
Also, I just deleted the rhel-debuginfo.repo and the error still persists.
Any sugesstions?
--
Rahul
No. What distro is in fact installed on this system? Did you 'upgrade'
from an official RHEL distro to a Fedora Core distro (something you
*probably* should not have done)? What does
cat /etc/*-release
display?
It also appears that don't have any sort of base distro repo files
installed in /etc/yum.repos.d. What is in /etc/yum.conf?
> No. What distro is in fact installed on this system? Did you
> 'upgrade' from an official RHEL distro to a Fedora Core distro
> (something you *probably* should not have done)? What does
Thanks again Robert. I thought that we had RHEL before and then we moved
on to Fedora. Maybe I was wrong. Sorry. Red Herring. I led you down the
wrong track.
Because like you expected it does show RHEL. But I still don't know why
I am getting the yum errors!
> cat /etc/*-release
>
> display?
Red Hat Enterprise Linux Server release 5.2 (Tikanga)
>
> It also appears that don't have any sort of base distro repo files
> installed in /etc/yum.repos.d. What is in /etc/yum.conf?
>
[main]
cachedir=/var/cache/yum
keepcache=0
debuglevel=2
logfile=/var/log/yum.log
distroverpkg=redhat-release
tolerant=1
exactarch=1
obsoletes=1
gpgcheck=1
plugins=1
# Note: yum-RHN-plugin doesn't honor this.
metadata_expire=1h
# Default.
# installonly_limit = 3
# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d
Any other debug sugesstions?
--
Rahul
OK, it appears that you do in fact has RHEL 5.2 installed, but it looks
like your service contract with RedHat has expired. Basically, this
means you cannot get updates from RedHat.
Given the above note, you probably have the yum-RHN-plugin installed and
it is detectig that your service contract with RedHat has expired and is
thus complaining.
You could try 'upgrading' to CentOS 5.2 or simply snarf the
yum-<mumble>.el5.centos and centos-release-5-2 rpms from a CentOS
mirror site (look on www.centos.org) and install these. This might let
you transition your system to CentOS 5.2 and let you continue with the
GPL updates (from the CentOS mirrors).
> OK, it appears that you do in fact has RHEL 5.2 installed, but it looks
> like your service contract with RedHat has expired. Basically, this
> means you cannot get updates from RedHat.
Ok. I'm calling up RH now to see if my account is indeed expired or
something else is up.
>
> You could try 'upgrading' to CentOS 5.2 or simply snarf the
> yum-<mumble>.el5.centos and centos-release-5-2 rpms from a CentOS
> mirror site (look on www.centos.org) and install these. This might let
> you transition your system to CentOS 5.2 and let you continue with the
> GPL updates (from the CentOS mirrors).
>
Meanwhile, what about the epel repo? Is that also RH or is that one free? I
do have another server on Centos but I think we re going to keep paying for
RHEL on this one.
Meanwhile of all the packages I have installed is there a way of finding
out which ones came from which repos? I was just curious how many I was
pulling from RHEL and how many from epel.
--
Rahul
>
> Robert Heller <hel...@deepsoft.com> wrote in
> news:cNmdneeVm4dUvB_U...@posted.localnet:
>
> > OK, it appears that you do in fact has RHEL 5.2 installed, but it looks
> > like your service contract with RedHat has expired. Basically, this
> > means you cannot get updates from RedHat.
> Ok. I'm calling up RH now to see if my account is indeed expired or
> something else is up.
>
> >
> > You could try 'upgrading' to CentOS 5.2 or simply snarf the
> > yum-<mumble>.el5.centos and centos-release-5-2 rpms from a CentOS
> > mirror site (look on www.centos.org) and install these. This might let
> > you transition your system to CentOS 5.2 and let you continue with the
> > GPL updates (from the CentOS mirrors).
> >
>
> Meanwhile, what about the epel repo? Is that also RH or is that one free? I
> do have another server on Centos but I think we re going to keep paying for
> RHEL on this one.
The epel repo is free -- it is a collection of packages from various
third parties, including rpmforge and others.
>
> Meanwhile of all the packages I have installed is there a way of finding
> out which ones came from which repos? I was just curious how many I was
> pulling from RHEL and how many from epel.
I don't think this is possible unless the package itself includes that
info (rpm -qi ...).