[Opendnssec-maintainers] Re: [Opendnssec-develop] WARNING: 1.4.0a1 appears in Red Hat Enterprise Linux repositories

Paul Wouters pwouters at redhat.com
Sun Jul 8 18:43:45 UTC 2012

On Sun, 8 Jul 2012, Jerry Lundström wrote:

Hi Jerry,

> I have pointed this out to him and posted on EPEL issue
> (https://bugzilla.redhat.com/show_bug.cgi?id=711899) that this is an
> ALPHA release and should not be pushed to production.

To ensure your repositories always have a "newer" version compared to
EPEL, please bump the epoch in your spec file and rebuild. This will
ensure your packages always have preference over the EPEL tree. If
Fedora/EPEL for whatever reason would need to set an epoch ourselves,
we would give everyone notice so they could take preventive action.

On Sun, Jul 8, 2012 at 2:55 PM, Roland van Rijswijk wrote:

> Hi all,
> A friendly warning: we are currently dealing with the fall out from what appears to be a stupid mistake by Red Hat. OpenDNSSEC 1.4.0a1 has appeared in repositories that are apparently configured on production systems by default. Consequently, our well-managed 1.3.9 install has been upgraded to 1.4.0a1 and all configuration has been wiped.

Note that rpm normally does not "wipe" configuration files, but creates
either .rpmnew files, or saves old configs as .rpmsave files. So I am
not sure what happened on that upgrade. Perhaps the custom spec files
used had not marked all the config files with "noreplace" in their spec
file? I am not sure what the rpm behaviour is when the non-epel spec file
does not mark a file as noreplace, and the epel spec file installing over
that. It could also be that different install paths are used. If someone
gives me a link to the spec file used, I can see if we can ensure this
would not happen in the future.

(I did not see any links to the spec/rpms at


More information about the Opendnssec-maintainers mailing list