Complete RHEL package lists?

Michael Stahnke mastahnke at
Sun Aug 26 17:56:24 UTC 2007

I  haven't forgotten about this topic, but I am still at a loss for
direction toward a solution.  I can use the RHN API to pull in a lot
of information about RHEL channels and such, but there are 400+
channels in RHN, and virtually no metadata.  I suppose the metadata
could somehow be derived, but that is a moving target.

I want to understand the total process before we dive in and try to
solve the problem.  Right now the problem from what I understand is:

Does an RHN channel already provide file : /usr/lib/foo ?

Are there other problems to tackle here?  What about obsoleting an
EL/RHN package?  Is that bad?


More information about the epel-devel-list mailing list