> Purely out of curiosity, I did try building libevent which failed
> miserably:-
>
> (...)
>
> For my part, I am not concerned about this as I am not using DNSTAP and
> only mention the issue in case others encounter it.
Ah, thanks for checking this. I was wrong - SRPMs for dnstap
dependencies
Best wishes,
Matthew
------
>From: Micha? K?pie?
>To: Matthew Richardson
>Cc: bind-users@lists.isc.org
>Date: Mon, 27 May 2019 13:12:36 +0200
>Subject: Re: isc-bind-esv Repository - "yum update" doing undesirable things!
>> Thank you for your most helpful advice.
> Thank you for your most helpful advice. On Centos 7, I have easily managed
> to build the non-scl packages using the following method starting with a
> default Centos 7 (I was using Linode) logged in as root:-
>
> (...)
>
> However, my luck is not quite as good with Centos 6 where my method is
of
installing the current Centos 6 Copr packages on the build machine, but
that did not assist.
Any guidance would be much appreciated.
With many thanks.
Best wishes,
Matthew
--
>From: Micha? K?pie?
>To: Matthew Richardson
>Cc: bind-users@lists.isc.org
>Date: Mon, 13 May 2
it to change the default Java version when multiple versions were
installed, and I didn't want the latest to be the default.
-Original Message-
From: bind-users On Behalf Of Michal Kepien
Sent: Monday, May 13, 2019 9:04 AM
To: Matthew Richardson
Cc: bind-users@lists.isc.org
Subject:
Matthew,
> The tools (dig etc) are used both manually and by a number of scripts.
> Following the upgrade without enabling SCL, dig (for example) was the
> previous version which came from the previous Copr package. Is there any
> official/recommended method for updating server to make the new to
0200
>Subject: Re: isc-bind-esv Repository - "yum update" doing undesirable things!
>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
>> u
After running some experiments, our plan is to make the SCL RPMs for the
upcoming set of releases (9.11.7, 9.14.2, 9.15.0; all due in two days)
use an FHS-compliant directory layout. Scriptlets in the revised RPMs
will attempt to adjust existing installations automatically, so that the
upgrade is
> I believe SCL allows multiple versions of the same package ... will ISC be
> using SCL in this manner?
If you are asking whether it will be possible to install multiple BIND
Software Collections side by side on the same machine, then no. All our
Copr repositories use the same Software Collecti
I believe SCL allows multiple versions of the same package ... will ISC be
using SCL in this manner?
Verne
--
Verne Britton, Lead Systems Programmervoice: (304) 293-5192 x230
Systems Support Group (in W
> If the old XPG4 and POSIX rules are to be at least paid some attention
> then the config data should be under /etc/opt/isc/named and the software
> binaries and libs stay in /opt/isc/named with logs going to the correct
> /var/opt/isc/named.
This is a good point, thanks for raising it. Software
> 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.
FWIW, currently publi
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
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
On 5/8/19 11:06 PM, Greg Rivers wrote:
On Wednesday, May 8, 2019 1:49:38 PM CDT Matthew Richardson wrote:
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 lates
On Wednesday, May 8, 2019 1:49:38 PM CDT Matthew Richardson wrote:
> 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
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.
17 matches
Mail list logo
