[EPEL-devel] Fedora EPEL 6 updates-testing report

[updates]

The following Fedora EPEL 6 Security updates need testing:
 Age  URL
 173  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b6c663378c   
unrtf-0.21.9-8.el6
  29  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-4b684248e8   
drupal7-7.60-2.el6
  12  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-307ddb503d   
php-PHPMailer-5.2.27-1.el6


The following builds have been pushed to Fedora EPEL 6 updates-testing

bird2-2.0.2-6.el6

Details about builds:



 bird2-2.0.2-6.el6 (FEDORA-EPEL-2018-b4eae8221c)
 BIRD Internet Routing Daemon

Update Information:

BIRD is a dynamic IP routing daemon supporting both, IPv4 and IPv6, Border
Gateway Protocol (BGPv4), Routing Information Protocol (RIPv2, RIPng), Open
Shortest Path First protocol (OSPFv2, OSPFv3), Babel Routing Protocol (Babel),
Bidirectional Forwarding Detection (BFD), IPv6 router advertisements, static
routes, inter-table protocol, command-line interface allowing on-line control
and inspection of the status of the daemon, soft reconfiguration as well as a
powerful language for route filtering.

References:

  [ 1 ] Bug #1653088 - Review Request: bird2 - BIRD Internet Routing Daemon
https://bugzilla.redhat.com/show_bug.cgi?id=1653088


___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org

[EPEL-devel] Re: EPEL6 conntrack-tools-0.9.13-3.el6.x86_64 metadata possibly incorrect

[John Griffin]

Hello Stephen,

What else can I do or provide to move this issue along.

Best regards,
[cid:image005.jpg@01D24A1F.439697B0]
John Griffin | Infrastructure Architect
815 NW 9th Street, Ste 221  |  Corvallis, OR 97330
P 541-768-4707
jgrif...@samhealth.org



From: John Griffin
Sent: Monday, November 19, 2018 8:47 AM
To: EPEL Development List 
Subject: [EPEL-devel] Re: EPEL6 conntrack-tools-0.9.13-3.el6.x86_64 metadata 
possibly incorrect





WARNING: This email originated from outside of SHS.  DO NOT CLICK ANY LINKS OR 
OPEN ATTACHMENTS unless you recognize the sender and know the contents are safe.



Hello Stephen,

Here is RH’s reply on the query as to how RH Satellite parses RPMs for date 
base filters.


Hi John, I got some information for you. Errata filter based on date does not 
scan RPMs, but scan errata (update or create) date and exclude/include all rpms 
which this specific errata contains. Does this help in the process?

Re:
[cid:image005.jpg@01D24A1F.439697B0]
John Griffin | Infrastructure Architect
815 NW 9th Street, Ste 221  |  Corvallis, OR 97330
P 541-768-4707
jgrif...@samhealth.org



From: John Griffin
Sent: Monday, November 5, 2018 8:34 AM
To: EPEL Development List 
mailto:epel-devel@lists.fedoraproject.org>>
Subject: [EPEL-devel] Re: EPEL6 conntrack-tools-0.9.13-3.el6.x86_64 metadata 
possibly incorrect





WARNING: This email originated from outside of SHS.  DO NOT CLICK ANY LINKS OR 
OPEN ATTACHMENTS unless you recognize the sender and know the contents are safe.



Hello Stephen,

We mirror the EPEL5 and EPEL7 repositories, but I really don’t know if there 
are other issues with those or EPEL6. The only reason I stumbled upon this one 
was due to the fact that the munin update in Sept 2018 now requires 
conntrack-tools. There may be others, and this also maybe be the only one.

I will request from RH the technical details they use when applying date 
filters in Satellite, maybe with that I can scan the other RPM’s in our mirrors 
for other hits.

Best Regards,
[cid:image005.jpg@01D24A1F.439697B0]
John Griffin | Infrastructure Architect
815 NW 9th Street, Ste 221  |  Corvallis, OR 97330
P 541-768-4707
jgrif...@samhealth.org



From: Stephen John Smoogen mailto:smo...@gmail.com>>
Sent: Thursday, November 1, 2018 2:04 PM
To: 
epel-devel@lists.fedoraproject.org
Subject: [EPEL-devel] Re: EPEL6 conntrack-tools-0.9.13-3.el6.x86_64 metadata 
possibly incorrect





WARNING: This email originated from outside of SHS.  DO NOT CLICK ANY LINKS OR 
OPEN ATTACHMENTS unless you recognize the sender and know the contents are safe.




On Thu, 1 Nov 2018 at 16:46, John Griffin 
mailto:jgrif...@samhealth.org>> wrote:

Hello Stephen,



Yes, we have the conntrack-tools in our Red Hat Satellite repository, and we 
can apply it outside of our Satellite process; by manually copying the rpm to 
each server and installing outside of our process.



The issue is the interworking of the metatdata in the conntrack-tools RPM and 
Red Hat Satellite date filters for Content Views. Not sure how familiar you are 
with Red Hat Satellite, but the data filters are the primary method used to 
create a cyclical patching schedule and thus patch sets based on date.



In Red Hat Satellite, if I specify any date inclusion (Like from January 1, 
1970 - October 12, 2018) and point it at the EPEL6 repository the filter does 
not pick up the conntrack-tools. I opened support case with Red Hat, and with 
their assistance we have a work around, where we don't specify any Satellite 
date filters for the EPEL repositories (i.e. Get Everything no matter when 
released) and yes still keep the Satellite date filters on the official Red Hat 
repositories used to create the combined  Satellite content view.



However this work-around does not allow us to recreate a patch content view of 
EPEL product or patches of any date other than 'today'. Without a date filter 
we get all EPEL content and patches. This does not work with our Patching 
paradigm, as we base patch sets on Date. We then use life-cycle management to 
promote a patch set to Production after it has been vetted on Dev then Test.



Red Hat does not support EPEL, and indicated this is not a Satellite issue but 
a RPM metadata issue with EPEL release process.


I will check but I am not sure it is a problem we can solve quickly as I don't 
know how Satellite categorizes dates currently. Do you also mirror anything 
from other non Red Hat Network repositories and do they have the problem also? 
[I am mostly looking to see if we are not setting something up we should or not]



Let me know if you need further clarification.



Best Regards,
[cid:image005.jpg@01D24A1F.439697B0]
John Griffin | Infrastructure Architect
815 NW 9th Street, Ste 221  |  Corvallis, OR 97330
P 541-768-4707
jgrif...@samhealth.org