isc-bind-esv Repository - "yum update" doing undesirable things!
Matthew Richardson
matthew-l at itconsult.co.uk
Mon May 27 14:47:27 UTC 2019
Dear Michal,
Again, thank you very much for your information and advice, which is most
appreciated.
As I only have a couple of Centos 6 servers remaining which do not use
DNSTAP, I got things working by using rpmbuild with "--without dnstap"
which worked very well for me.
Purely out of curiosity, I did try building libevent which failed
miserably:-
>[root at li1523-85 ~]# rpmbuild --rebuild --define 'dist .el6' --without scl isc-bind-libevent-2.1.8-6.el6.src.rpm
>Installing isc-bind-libevent-2.1.8-6.el6.src.rpm
>warning: InstallSourcePackage at: psm.c:244: Header V3 RSA/SHA1 Signature, key ID 4168cd93: NOKEY
>warning: user mockbuild does not exist - using root
>warning: group mock does not exist - using root
>warning: user mockbuild does not exist - using root
>warning: group mock does not exist - using root
>warning: user mockbuild does not exist - using root
>warning: group mock does not exist - using root
>Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.i9w0GF
>+ umask 022
>+ cd /root/rpmbuild/BUILD
>+ LANG=C
>+ export LANG
>+ unset DISPLAY
>+ cd /root/rpmbuild/BUILD
>+ rm -rf isc-bind-libevent-2.1.8-stable
>+ /usr/bin/gzip -dc /root/rpmbuild/SOURCES/libevent-2.1.8-stable.tar.gz
>+ /bin/tar -xf -
>+ STATUS=0
>+ '[' 0 -ne 0 ']'
>+ cd isc-bind-libevent-2.1.8-stable
>/var/tmp/rpm-tmp.i9w0GF: line 38: cd: isc-bind-libevent-2.1.8-stable: No such file or directory
>error: Bad exit status from /var/tmp/rpm-tmp.i9w0GF (%prep)
>
>
>RPM build errors:
> InstallSourcePackage at: psm.c:244: Header V3 RSA/SHA1 Signature, key ID 4168cd93: NOKEY
> user mockbuild does not exist - using root
> group mock does not exist - using root
> user mockbuild does not exist - using root
> group mock does not exist - using root
> user mockbuild does not exist - using root
> group mock does not exist - using root
> Bad exit status from /var/tmp/rpm-tmp.i9w0GF (%prep)
>[root at li1523-85 ~]# ls /root/rpmbuild/BUILD
>libevent-2.1.8-stable
>[root at li1523-85 ~]# ls /root/rpmbuild/SOURCES
>libevent-2.1.8-stable.tar.gz libevent-nonettests.patch
>[root at li1523-85 ~]#
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.
Best wishes,
Matthew
------
>From: Micha? K?pie? <michal at isc.org>
>To: Matthew Richardson <matthew-l at itconsult.co.uk>
>Cc: bind-users at 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. 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
>> similar:-
>>
>> (...)
>>
>> but the rpmbuild fails due to a couple of missing dependencies:-
>>
>> (...)
>
>What you are observing is one of the reasons we decided to provide our
>own packages - namely, that building BIND with dnstap support on a
>platform which does not readily supply all relevant build requirements
>is a bit of a pain in the neck. The reason your CentOS 7 build
>succeeded is that EPEL 7 contains the required build dependencies for
>dnstap support in BIND; EPEL 6 lacks these and thus the build fails.
>
>> Thus far, I have failed on Centos 6 to identify how or where to install
>> these two depedencies, for which I would ideally like a package rather than
>> compiling from source.
>
>You have two options here:
>
> - build without dnstap support, by using "--without dnstap",
>
> - make the build requirements available in the build environment, most
> likely by first building them from source as well (you can use the
> SRPMs in our Coprs for convenience), in this order:
>
> 1. libevent
> 2. fstrm
> 3. protobuf
> 4. protobuf-c
>
>> I have tried (what I thought was obvious) of
>> installing the current Centos 6 Copr packages on the build machine, but
>> that did not assist.
>
>The development packages in our Coprs can only be used for building a
>Software Collection [1]. Thus, installing them as they are will not
>allow you to compile a non-SCL version of BIND with dnstap support.
>
>Hope this helps!
>
>[1]: unless you rebuild them using "--without scl", of course
More information about the bind-users
mailing list