<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div dir="auto">
<div>While it is an understood intent to move to scl, it is not nesseraly a welcome change for all.</div>
<div dir="auto">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.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Anyways, highly appreciated the idea of releasing prebuilt packages to the community.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Best,</div>
<div dir="auto">Dmitry<br>
<div class="gmail_extra" dir="auto"><br>
<div class="gmail_quote">On May 9, 2019 12:20 AM, Michał Kępień <michal@isc.org> wrote:<br type="attribution">
<blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><font size="2"><span style="font-size:11pt">
<div>Hi Matthew,<br>
<br>
> I have been using the isc-bind-esv repository on Centos 7 since it was<br>
> created. On each upgrade, a "yum update" has done the correct thing by<br>
> upgrading from the running version to the latest version.<br>
> <br>
> Today (happily on a cloned test server!) I repeated this with the upgrade<br>
> being from 9.11.6 to 9.11.6.P1-1.2.el7.<br>
> <br>
> It seems that the package names have changed and that Bind is now installed<br>
> in a new directory structure below /opt/isc. In my case, a previously<br>
> working authoratitive configuration is now comprehensively broken.<br>
> <br>
> Before troubleshooting, I was wondering whether I had missed any release<br>
> notes or similar which might explain what is going on.<br>
<br>
First of all, thanks for trying these packages out and apologies for the<br>
trouble caused. This is an intentional change in a repository which ISC<br>
has always been describing as experimental [1].<br>
<br>
A few months ago, we decided that Software Collections [2] are the<br>
preferred long-term solution for our RPM packages. Among other things,<br>
this was prompted by the package conflicts people were running into when<br>
using our Coprs [3]. What you observed on your server is an update from<br>
non-SCL packages to SCL packages.<br>
<br>
To make your previous setup work with SCL packages, please move your<br>
/etc/named.conf to /opt/isc/isc-bind/root/etc/named.conf. If you<br>
previously enabled named startup upon boot and you still want that to be<br>
the case, please run:<br>
<br>
systemctl start isc-bind-named<br>
<br>
BIND utilities (e.g. dig, rndc) are available after enabling the<br>
Software Collection, for example using:<br>
<br>
scl enable isc-bind bash<br>
<br>
This disruption was a one-off - we plan to soon move our Copr<br>
repositories away from their current experimental status. Once that<br>
happens, care will be taken not to break existing installations.<br>
<br>
Once again, apologies for the inconvenience. If you have any further<br>
questions, please feel free to ask them.<br>
<br>
Hope this helps,<br>
<br>
[1] See <a href="https://www.isc.org/blogs/bind-9-packages/">https://www.isc.org/blogs/bind-9-packages/</a> and the description<br>
of the Copr itself.<br>
<br>
[2] <a href="https://www.softwarecollections.org/">https://www.softwarecollections.org/</a><br>
<br>
[3] <a href="https://lists.isc.org/pipermail/bind-users/2019-January/101277.html">
https://lists.isc.org/pipermail/bind-users/2019-January/101277.html</a>,<br>
for example<br>
<br>
-- <br>
Best regards,<br>
Michał Kępień<br>
_______________________________________________<br>
Please visit <a href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a> to unsubscribe from this list<br>
<br>
bind-users mailing list<br>
bind-users@lists.isc.org<br>
<a href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a><br>
</div>
</span></font></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</body>
</html>