On Wed, 31 Oct 2018 at 16:01, John Griffin <jgriffin(a)samhealth.org> wrote:
We now use Red Hat Satellite 6.3 and have it synchronizing to
https://dl.fedoraproject.org/pub/epel/6Server/
Recent updates to munin-node and munin-common require conntrack-tools x86_64
0.9.13-3.el6.
The conntrack-tools x86_64 0.9.13-3.el6 was release in May 2014, based on rpm -qip, and
is in our synchronized EPEL content view on our Satellite.
We use content view date filters to only select errata (patches) up to a specific date
(based on our patch cycle) and publish new content views based on said dates. We stumbled
upon the issue that the conntrack-tools x86_64 0.9.13-3.el6 package not being included in
the content view, even though it existed in the repository, and our date based content
filter should have encompassed the release date of the package. This caused yum update to
fail for the munin updates, as the prerequisite could not be satisfied.
I need more information like what you are exactly seeing. The
conntrack-tools is in the repository and can be downloaded and
installed via yum and reposync.
Curious if there is indeed something amiss with this packages
metadata, and also if other EPEL packages suffer the same fate. We are concerned that we
will not be able to rely on the veracity of EPEL packages and will have to mitigate this
in some fashion.
_______________________________________________
epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org
To unsubscribe send an email to epel-devel-leave(a)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.fedoraproj...
--
Stephen J Smoogen.