Testing EPEL packages

A 5 star hangout for overworked and underpaid system admins.
Post Reply
User avatar
Retired Moderator
Posts: 3046
Joined: 2010/12/01 19:25:52
Location: Helsinki, Finland

Testing EPEL packages

Post by avij » 2018/09/12 12:21:20

This is not directly related to CentOS, therefore I'm posting this in the CentOS Social subforum.

If you are using packages from EPEL, please consider enabling the epel-testing repository on your development/testing systems. You should also run yum update periodically on those systems. That way there would be a higher probability of noticing any problems in the packages before they get submitted to the main (stable) epel repository.

You can enable the epel-testing repository with yum-config-manager --enable epel-testing or by editing /etc/yum.repos.d/epel-testing.repo to have enabled=1.

If you do find a problem with a package in epel-testing, you should submit feedback on the package. The feedback page can be found based on the source rpm name of the package. For example, if you think there is a problem with uwsgi-plugin-python2, you can run rpm -qi uwsgi-plugin-python2 and find the "Source RPM" line. Alternatively, you can run repoquery --source uwsgi-plugin-python2 if you were not able to install the package, for example due to missing dependencies. In this example the source rpm name is uwsgi and the package's overview page is at https://src.fedoraproject.org/rpms/uwsgi

From there you can find the Updates status tab, and from there, each update that has been build. You can give anonymous feedback to report problems, but only users who are logged in can affect the karma.

If you find a problem with a package that is already in stable, the proper way to report problems is via Red Hat's Bugzilla (New bug > Fedora > Fedora EPEL).

On a more positive note, if you have the epel-testing repository enabled and the package from epel-testing seems to be working fine, please give positive karma to make the package move to stable quicker.


Post Reply