[EPEL-devel] [EPEL] #7: Policy and technical means for removing orphaned packages in EPEL

[EPEL]

#7: Policy and technical means for removing orphaned packages in EPEL
-----------------------------+----------------------------
  Reporter:  smooge          |      Owner:  epel-wranglers
      Type:  task            |     Status:  new
  Priority:  major           |  Milestone:
 Component:  Policy problem  |    Version:
Resolution:                  |   Keywords:
-----------------------------+----------------------------

Comment (by till):

 Replying to [comment:2 smooge]:
 > Till. Thanks for offering. I am expecting we will be setting up a
 practice orphan and removal in early December to try and script this. The
 main thing is going to be how far does the recursion go when we remove all
 these packages?

 Since you announced that all packages with broken dependencies are to be
 removed, I suggest to first retire all removed orphans and then use the
 repoclosure output from the following days to retire the remaining
 packages with broken dependencies. This will also take into account if
 dependencies are provided by RHEL/CentOS and orphaned EPEL packages (e.g.
 if a package was orphaned but not retired when a package moved from EPEL
 to RHEL). My script only looks at the EPEL packages.

-- 
Ticket URL: <https://fedorahosted.org/epel/ticket/7#comment:3>
EPEL <https://fedoraproject.org/wiki/EPEL>
Extra Packages for Enterprise Linux