Re: [EPEL-devel] [EPEL] #25: Automated dependency testing

[EPEL]

#25: Automated dependency testing
-----------------------------+------------------
  Reporter:  avij            |      Owner:  avij
      Type:  enhancement     |     Status:  new
  Priority:  minor           |  Milestone:
 Component:  Policy problem  |    Version:
Resolution:                  |   Keywords:  QA
-----------------------------+------------------

Comment (by avij):

 bstinson asked me to open a ticket for this task, so here it is. I suppose
 this ticket can be used for determining what would be the best solution
 for automatically detecting broken dependencies. Today's case of munin and
 perl-Net-CIDR showed that we'd need to find some sort of a solution to
 this problem.

 I'm sure Taskotron would fulfill this need much more elegantly than my 15
 lines of shell script. Taskotron was discussed in some earlier meeting,
 but it wasn't quite ready yet at that time. Perhaps it can be enabled for
 EPEL now, or when the orphan packages have been purged in December. There
 are folks who know the Taskotron situation much better than I do.

 Until the switch to Taskotron happens, I'll be happy to take care of
 notifying packagers of broken EPEL dependencies using my own script.

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