#25: Automated dependency testing
----------------------------+------------------
Reporter: avij | Owner: avij
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Policy problem | Version:
Keywords: QA |
----------------------------+------------------
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.
--
Ticket URL: <https://fedorahosted.org/epel/ticket/25>
EPEL <https://fedoraproject.org/wiki/EPEL>
Extra Packages for Enterprise Linux
_______________________________________________
epel-devel mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
