The following Fedora EPEL 7 Security updates need testing:
Age URL
29
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2748/nodejs-0.10.32-1.el7,v8-3.14.5.10-14.el7
28
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2861/nodejs-qs-0.6.6-3.el7
28
The following Fedora EPEL 5 Security updates need testing:
Age URL
914
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5630/bugzilla-3.2.10-5.el5
368
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11893/libguestfs-1.20.12-1.el5
133
#8: EPEL-latest link rpm
-+
Reporter: smooge | Owner: epel-wranglers
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Policy problem |Version:
Resolution:
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If
In going through some of the security updates for EPEL 7, I've noticed a
few quirks, and I'm unsure of the cause/design.
Example - https://apps.fedoraproject.org/packages/nginx
This does not show an EPEL7 build, even though there clearly is one (and
it's flagged for a security update
