isc-bind-esv Repository - "yum update" doing undesirable things!

[Dmitry Vayntrub]

While it is an understood intent to move to scl, it is not nesseraly a welcome change for all.
We were excited and were hoping to start using ISB BIND rpm's as they used to be prior to the latest build, but I guess we will have to continue building our own rpm's.

Anyways, highly appreciated the idea of releasing prebuilt packages to the community.

Best,
Dmitry

On May 9, 2019 12:20 AM, Michał Kępień <michal at isc.org> wrote:
Hi Matthew,

> I have been using the isc-bind-esv repository on Centos 7 since it was
> created.  On each upgrade, a "yum update" has done the correct thing by
> upgrading from the running version to the latest version.
>
> Today (happily on a cloned test server!) I repeated this with the upgrade
> being from 9.11.6 to 9.11.6.P1-1.2.el7.
>
> It seems that the package names have changed and that Bind is now installed
> in a new directory structure below /opt/isc.  In my case, a previously
> working authoratitive configuration is now comprehensively broken.
>
> Before troubleshooting, I was wondering whether I had missed any release
> notes or similar which might explain what is going on.

First of all, thanks for trying these packages out and apologies for the
trouble caused.  This is an intentional change in a repository which ISC
has always been describing as experimental [1].

A few months ago, we decided that Software Collections [2] are the
preferred long-term solution for our RPM packages.  Among other things,
this was prompted by the package conflicts people were running into when
using our Coprs [3].  What you observed on your server is an update from
non-SCL packages to SCL packages.

To make your previous setup work with SCL packages, please move your
/etc/named.conf to /opt/isc/isc-bind/root/etc/named.conf.  If you
previously enabled named startup upon boot and you still want that to be
the case, please run:

    systemctl start isc-bind-named

BIND utilities (e.g. dig, rndc) are available after enabling the
Software Collection, for example using:

    scl enable isc-bind bash

This disruption was a one-off - we plan to soon move our Copr
repositories away from their current experimental status.  Once that
happens, care will be taken not to break existing installations.

Once again, apologies for the inconvenience.  If you have any further
questions, please feel free to ask them.

Hope this helps,

[1] See https://www.isc.org/blogs/bind-9-packages/ and the description
    of the Copr itself.

[2] https://www.softwarecollections.org/

[3] https://lists.isc.org/pipermail/bind-users/2019-January/101277.html,
    for example

--
Best regards,
Michał Kępień
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
bind-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20190509/9d9c178b/attachment.html>