On Fri, 10 Feb 2012 21:17:47 +0100 Till Maas <[email protected]> wrote:
> On Thu, Feb 09, 2012 at 05:21:56PM -0500, Tom Diehl wrote: > > On Thu, 9 Feb 2012, Till Maas wrote: > > > > >On Thu, Feb 09, 2012 at 03:29:40PM -0500, Tom Diehl wrote: > > > > > >>Currently, how can I tell if there are any other epel packages > > >>that have been orphaned? > > > > > >You can inspect the list that the following command generates on > > >your server: > > >package-cleanup --orphans > > > > I was not aware of that command so I took a look at it. Correct me > > if I am wrong but I think that just tells if there is an rpm in any > > of the configured repos. With mediawiki package-cleanup shows > > nothing since the original mediawiki rpm is still in the repo. > > > > Am I missing something? > > Sorry, this was my fault. I assumed that orphaned packages are removed > from the repo. But maybe this shows a proper way to deal with this > issue: Create a new EPEL repo called epel-orphans or similar, disable > it by default and move all orphaned packages there. Then users can > still get the lastest orphaned package by enabling epel-orphans and > package-cleanup --orphans can be used. They should be removed from the repos. Looks like mediawiki wasn't retired correctly. It's orphaned, but you need to also request it being blocked by rel-eng. kevin
signature.asc
Description: PGP signature
_______________________________________________ epel-devel-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/epel-devel-list
