#25 Automated dependency testing
Opened 6 years ago by avij. Modified 4 years ago

It has happened way too often that packages are pushed to testing, then they spend the next 14 days in testing but nobody bothers testing them, and then finally the package owner pushes them to stable. At this point people notice that the package would need some dependant packages and chaos ensues.

To combat this, I have written a script that does nightly dependency testing for packages in epel and epel-testing, and mails me the diff from previous night's run. The script is basically just a "repoclosure -r base -r updates -r epel -r epel-testing" for each of EPEL 5,6,7. My plan is to give bad karma to those packages in epel-testing that have dependency problems. This should alert the package owner to not push the package to stable before the dep problems have been resolved. When the dependency problem has been resolved (one way or another), this will show up on the next list and I can give good karma to that package to clear the previous bad karma. Eventually giving this good/bad karma would need to be fully automated, but this is a start.

Testting this is a good idead. If you would like to pursue this, I recommend looking at https://fedoraproject.org/wiki/Taskotron which is an framework for doing these kind of automatic tests. I is already used for Fedora, maybe it can be activated for EPEL as well.

Btw. what is it you want to be handled/discussed in this ticket?

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.

Login to comment on this ticket.