From qboosh at pld-linux.org Sat Jul 14 09:00:03 2018 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Sat, 14 Jul 2018 09:00:03 +0200 Subject: no e-mails from th-i686 builder Message-ID: <20180714070003.GA7451@mail> When sending requests, I receive e-mail reports only from th-x32 and th-x86_64 builders, but not th-i686. Could it be fixed, so that I won't miss i686 build failure (without having to look at buildlogs site each time)? -- Jakub Bogusz http://qboosh.pl/ From arekm at maven.pl Sat Jul 14 18:52:09 2018 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Sat, 14 Jul 2018 18:52:09 +0200 Subject: no e-mails from th-i686 builder In-Reply-To: <20180714070003.GA7451@mail> References: <20180714070003.GA7451@mail> Message-ID: <201807141852.09507.arekm@maven.pl> On Saturday 14 of July 2018, Jakub Bogusz wrote: > When sending requests, I receive e-mail reports only from th-x32 and > th-x86_64 builders, but not th-i686. > > Could it be fixed, so that I won't miss i686 build failure (without > having to look at buildlogs site each time)? Should be fixed now. -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From qboosh at pld-linux.org Sun Jul 15 10:56:41 2018 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Sun, 15 Jul 2018 10:56:41 +0200 Subject: /etc/localtime missing on th-i686 builder Message-ID: <20180715085641.GA12810@mail> Could it be fixed? Other builders have /etc/localtime pointing to /usr/share/zoneinfo/Europe/Warsaw Lack of /etc/localtime could trigger some issues and is probably causing python-dateutil tests failure (which don't happen on carme-i686 after fixing glibc bug). On Sun, Jul 15, 2018 at 08:53:17AM +0000, PLD th-i686 builder wrote: > COMMAND (): FAILED > > --- COMMAND:: > Build-Time: user:0.01s sys:0.01s real:0.04s (faults io:0 non-io:1999) > > > > *** buildlog for COMMAND > ls: cannot access '/etc/localtime': No such file or directory > Begin-PLD-Builder-Info > Build-Time: user:0.01s sys:0.01s real:0.04s (faults io:0 non-io:1999) > > End-PLD-Builder-Info > -- Jakub Bogusz http://qboosh.pl/ From arekm at maven.pl Sun Jul 15 11:11:44 2018 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Sun, 15 Jul 2018 11:11:44 +0200 Subject: /etc/localtime missing on th-i686 builder In-Reply-To: <20180715085641.GA12810@mail> References: <20180715085641.GA12810@mail> Message-ID: <201807151111.45086.arekm@maven.pl> On Sunday 15 of July 2018, Jakub Bogusz wrote: > Could it be fixed? > Other builders have /etc/localtime pointing to > /usr/share/zoneinfo/Europe/Warsaw Fixed. -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From glen at delfi.ee Mon Jul 16 10:10:07 2018 From: glen at delfi.ee (Elan Ruusamae) Date: Mon, 16 Jul 2018 11:10:07 +0300 Subject: openssh user@ vs -l precedence Message-ID: <82c3cce5-410e-6b01-cb32-4ef96f31c027@delfi.ee> seems 7.7p1 introduced breaking change where if both user@ and -l provided used to work: GIT_SSH=wrapper ssh git at github.com where wrapper is: user=${SUDO_USER:-$USER} exec ssh -x -a -oClearAllForwardings=yes -l $user ${1:+"$@"} how it attempts to authenticate using glen@ not git@ $ git fetch upstream glen at github.com: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. $ git remote -v|grep ups upstream??????? git at github.com:eventum/eventum.git (fetch) upstream??????? git at github.com:eventum/eventum.git (push) $ rpm -q openssh --blink openssh-7.7p1-1.x86_64.rpm ??????? <= openssh-7.6p1-3.x86_64.rpm From glen at delfi.ee Mon Jul 16 10:28:43 2018 From: glen at delfi.ee (Elan Ruusamae) Date: Mon, 16 Jul 2018 11:28:43 +0300 Subject: ftp: .metadata accessibility Message-ID: <943bc16f-3beb-fff9-47d9-f15240187fef@delfi.ee> could someone take look and make .metadata folder accessible publicly? https://github.com/repology/repology-rules/issues/41#issuecomment-405178546 or maybe just rename it without dot? From glen at delfi.ee Mon Jul 16 11:00:28 2018 From: glen at delfi.ee (Elan Ruusamae) Date: Mon, 16 Jul 2018 12:00:28 +0300 Subject: Missing packages In-Reply-To: <20180626204634.usa32jzsapkucl52@kalarepa> References: <2ff23638-687c-4de3-b4a2-788f35d3fcec@pld.src.builder> <20180626204634.usa32jzsapkucl52@kalarepa> Message-ID: On 6/26/18 11:46 PM, Jan Palus wrote: > On 25.06.2018 17:14, PLD th-x86_64 builder wrote: >> NetworkManager-applet.spec (HEAD): OK >> >> --- NetworkManager-applet.spec:HEAD: >> upgrading packages >> Preparing... ################################################## >> NetworkManager-gtk-lib ################################################## >> Build-Time: user:105.32s sys:24.10s real:76.05s (faults io:19 non-io:8340882) >> >> Files queued for ftp: >> 1971561 NetworkManager-applet-debuginfo-1.8.14-1.x86_64.rpm >> 27747 NetworkManager-gtk-lib-apidocs-1.8.14-1.x86_64.rpm >> 20568 NetworkManager-gtk-lib-devel-1.8.14-1.x86_64.rpm >> 123330 NetworkManager-gtk-lib-1.8.14-1.x86_64.rpm >> 1020520 NetworkManager-applet-1.8.14-1.x86_64.rpm >> 341 NetworkManager-applet-1.8.14-1.src.rpm.uploadinfo > Yesterday I've managed to update one machine with new packages but today > they are gone from ftp. Any idea what happened to them? also chef-11 package missing. altho th-main still has ruby-2.3 From zawadaa at gmail.com Wed Jul 18 10:18:00 2018 From: zawadaa at gmail.com (Andrzej Zawadzki) Date: Wed, 18 Jul 2018 10:18:00 +0200 Subject: New NM 1.12 and OVPN Message-ID: After upgrade to newest version of NM, plugin NetworkManager-openvpn-1.8.4-1 doesn't work. Plugin is too old? -- Andrzej -------------- next part -------------- A non-text attachment was scrubbed... Name: kldofmclimhdmkni.png Type: image/png Size: 17539 bytes Desc: not available URL: From atler at pld-linux.org Wed Jul 18 10:37:30 2018 From: atler at pld-linux.org (Jan Palus) Date: Wed, 18 Jul 2018 10:37:30 +0200 Subject: New NM 1.12 and OVPN In-Reply-To: References: Message-ID: <20180718083730.7f2fvw3twpqh5kpa@kalarepa> On 18.07.2018 10:18, Andrzej Zawadzki wrote: > After upgrade to newest version of NM, plugin > NetworkManager-openvpn-1.8.4-1 doesn't work. > Plugin is too old? Try NetworkManager-1.12.0-2 once it's built. As a quick workaround in current release you can use: nmcli c up From zawadaa at gmail.com Wed Jul 18 16:14:15 2018 From: zawadaa at gmail.com (Andrzej Zawadzki) Date: Wed, 18 Jul 2018 16:14:15 +0200 Subject: New NM 1.12 and OVPN In-Reply-To: <20180718083730.7f2fvw3twpqh5kpa@kalarepa> References: <20180718083730.7f2fvw3twpqh5kpa@kalarepa> Message-ID: On 18.07.2018 10:37, Jan Palus wrote: On 18.07.2018 10:18, Andrzej Zawadzki wrote: After upgrade to newest version of NM, plugin NetworkManager-openvpn-1.8.4-1 doesn't work. Plugin is too old? Try NetworkManager-1.12.0-2 once it's built. As a quick workaround in current release you can use: nmcli c up Thanks! New version is working correctly. -- Andrzej From qboosh at pld-linux.org Wed Jul 18 16:44:01 2018 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Wed, 18 Jul 2018 16:44:01 +0200 Subject: [packages/rpcbind] - use upstream systemd units (with patch); real life check wanted - use upstream make install In-Reply-To: <929674db-e461-a160-b08a-19e338c31741@gmail.com> References: <743aa2864e361cc9aabb9e1365975d257d2ff599_refs_heads_master@pld-linux.org> <929674db-e461-a160-b08a-19e338c31741@gmail.com> Message-ID: <20180718144401.GA27502@mail> On Thu, Jun 14, 2018 at 12:18:27PM +0200, Andrzej Zawadzki wrote: > Hi! > Doesn't work :-( > [root at pld-template ~]# systemctl status nfslock > 0M nfslock.service - NFS file locking service > Loaded: loaded (/lib/systemd/system/nfslock.service; enabled; vendor > preset: enabled) > Active: failed (Result: exit-code) since Thu 2018-06-14 10:42:18 > CEST; 4min 6s ago > Process: 874 ExecStopPost=/sbin/sysctl -w fs.nfs.nlm_tcpport=0 > fs.nfs.nlm_udpport=0 (code=exited, status=254) > Process: 815 ExecStart=/sbin/rpc.statd $STATDOPTIONS (code=exited, > status=1/FAILURE) > Process: 808 ExecStartPre=/usr/share/nfs-utils/nfslock.preconfig > (code=exited, status=0/SUCCESS) > cze 14 10:42:18 pld-template rpc.statd[826]: Failed to register (statd, > 1, udp): svc_reg() err: RPC: Success > cze 14 10:42:18 pld-template rpc.statd[826]: Failed to register (statd, > 1, tcp): svc_reg() err: RPC: Success > cze 14 10:42:18 pld-template rpc.statd[826]: Failed to register (statd, > 1, udp6): svc_reg() err: RPC: Success > cze 14 10:42:18 pld-template rpc.statd[826]: Failed to register (statd, > 1, tcp6): svc_reg() err: RPC: Success > cze 14 10:42:18 pld-template rpc.statd[826]: failed to create RPC > listeners, exiting Any ideas on the cause? > cze 14 10:42:18 pld-template systemd[1]: nfslock.service: Control > process exited, code=exited status=1 > cze 14 10:42:18 pld-template sysctl[874]: sysctl: cannot stat > /proc/sys/fs/nfs/nlm_tcpport: No such file or directory > cze 14 10:42:18 pld-template sysctl[874]: sysctl: cannot stat > /proc/sys/fs/nfs/nlm_udpport: No such file or directory Some module not loaded? > cze 14 10:42:18 pld-template systemd[1]: nfslock.service: Failed with > result 'exit-code'. > cze 14 10:42:18 pld-template systemd[1]: Failed to start NFS file > locking service. > After downgrade to auto/th/rpcbind-0.2.3-1 everything works. > On 11.04.2018 19:50, qboosh wrote: > > commit 743aa2864e361cc9aabb9e1365975d257d2ff599 > Author: Jakub Bogusz [1] > Date: Wed Apr 11 19:50:57 2018 +0200 > > - use upstream systemd units (with patch); real life check wanted > - use upstream make install > > rpcbind-systemd.patch | 29 +++++++++++++++++++++++++++++ > rpcbind.service | 13 ------------- > rpcbind.socket | 8 -------- > rpcbind.spec | 23 ++++++++++------------- > 4 files changed, 39 insertions(+), 34 deletions(-) > --- > diff --git a/rpcbind.spec b/rpcbind.spec > index 5493666..544fe5a 100644 > --- a/rpcbind.spec > +++ b/rpcbind.spec > @@ -9,12 +9,11 @@ Source0: [2]http://downloads.sourceforge.net/rpcbind/%{na > me}-%{version}.tar.bz2 > # Source0-md5: cf10cd41ed8228fc54c316191c1f07fe > Source1: %{name}.init > Source2: %{name}.sysconfig > -Source3: %{name}.service > -Source4: %{name}.socket > Patch0: %{name}-libwrap.patch > Patch1: %{name}-syslog.patch > Patch2: %{name}-sunrpc.patch > Patch3: %{name}-nss.h.patch > +Patch4: %{name}-systemd.patch > Patch6: %{name}-tcp-addrs.patch > # [3]http://nfsv4.bullopensource.org/doc/tirpc_rpcbind.php > URL: [4]http://sourceforge.net/projects/rpcbind/ > @@ -57,6 +56,7 @@ wywol/ania RPC na serwerze na tej maszynie. > %patch1 -p1 > %patch2 -p1 > %patch3 -p1 > +%patch4 -p1 > %patch6 -p1 > > %build > @@ -65,29 +65,26 @@ wywol/ania RPC na serwerze na tej maszynie. > %{__autoconf} > %{__automake} > %configure \ > + --bindir=/sbin \ > --enable-libwrap \ > --enable-warmstarts \ > --with-statedir=/var/lib/rpcbind \ > --with-rpcuser=rpc \ > - --with-systemdsystemunitdir=%{%systemdunitdir} > + --with-systemdsystemunitdir=%{systemdunitdir} > %{__make} > > %install > rm -rf $RPM_BUILD_ROOT > -install -d $RPM_BUILD_ROOT{/sbin,%{_sbindir},/etc/{sysconfig,rc.d/init.d}} \ > - $RPM_BUILD_ROOT{%{_mandir}/man8,%{_var}/lib/%{name},%{systemdunitdir}} > +install -d $RPM_BUILD_ROOT{/sbin,%{_sbindir},/etc/{sysconfig,rc.d/init.d},/var/ > lib/rpcbind} > > -install rpcbind $RPM_BUILD_ROOT/sbin > -install rpcinfo $RPM_BUILD_ROOT%{_sbindir} > +%{__make} install \ > + DESTDIR=$RPM_BUILD_ROOT > > -install man/{rpcbind,rpcinfo}.8 $RPM_BUILD_ROOT%{_mandir}/man8 > +%{__mv} $RPM_BUILD_ROOT/sbin/rpcinfo $RPM_BUILD_ROOT%{_sbindir} > > install %{SOURCE1} $RPM_BUILD_ROOT/etc/rc.d/init.d/rpcbind > install %{SOURCE2} $RPM_BUILD_ROOT/etc/sysconfig/rpcbind > > -install %{SOURCE3} $RPM_BUILD_ROOT%{systemdunitdir}/rpcbind.service > -install %{SOURCE4} $RPM_BUILD_ROOT%{systemdunitdir}/rpcbind.socket > - > %clean > rm -rf $RPM_BUILD_ROOT > > @@ -115,8 +112,8 @@ fi > %triggerpostun -- %{name} < 0.2.0-5 > if [ -f /etc/sysconfig/rpcbind ]; then > . /etc/sysconfig/rpcbind > - [ "$RPCBIND_VERBOSE" == "no" ] || RPCBIND_OPTIONS="-l" > - [ "$RPCBIND_INSECURE" == "yes" ] && RPCBIND_OPTIONS="$RPCBIND_OPTIONS -i > " > + [ "$RPCBIND_VERBOSE" = "no" ] || RPCBIND_OPTIONS="-l" > + [ "$RPCBIND_INSECURE" = "yes" ] && RPCBIND_OPTIONS="$RPCBIND_OPTIONS -i" > for a in $RPCBIND_ADDRESSES ; do > RPCBIND_OPTIONS="$RPCBIND_OPTIONS -h $a" > done > diff --git a/rpcbind-systemd.patch b/rpcbind-systemd.patch > new file mode 100644 > index 0000000..c38ca9c > --- /dev/null > +++ b/rpcbind-systemd.patch > @@ -0,0 +1,29 @@ > +--- rpcbind-0.2.4/systemd/rpcbind.service.in.orig 2016-11-28 21:47:28.0000 > 00000 +0100 > ++++ rpcbind-0.2.4/systemd/rpcbind.service.in 2018-04-11 19:41:46.466605338 +0 > 200 > +@@ -6,12 +6,13 @@ > + # Make sure we use the IP addresses listed for > + # rpcbind.socket, no matter how this unit is started. > + Wants=rpcbind.socket > +-After=rpcbind.socket > ++After=rpcbind.socket syslog.target network.target > + > + [Service] > + Type=notify > +-# distro can provide a drop-in adding EnvironmentFile=-/??? if needed. > ++EnvironmentFile=-/etc/sysconfig/rpcbind > + ExecStart=@_bindir@/rpcbind $RPCBIND_OPTIONS -w -f > + > + [Install] > + WantedBy=multi-user.target > ++Also=rpcbind.socket > +--- rpcbind-0.2.4/systemd/rpcbind.socket.orig 2016-11-28 21:47:28.000000000 +0 > 100 > ++++ rpcbind-0.2.4/systemd/rpcbind.socket 2018-04-11 19:43:27.366604185 +0 > 200 > +@@ -5,7 +5,7 @@ > + Before=rpcbind.target > + > + [Socket] > +-ListenStream=/run/rpcbind.sock > ++ListenStream=/var/run/rpcbind.sock > + > + # RPC netconfig can't handle ipv6/ipv4 dual sockets > + BindIPv6Only=ipv6-only > diff --git a/rpcbind.service b/rpcbind.service > deleted file mode 100644 > index fab7898..0000000 > --- a/rpcbind.service > +++ /dev/null > @@ -1,13 +0,0 @@ > -[Unit] > -Description=RPC bind service > -Requires=rpcbind.socket > -After=syslog.target network.target > - > -[Service] > -Type=forking > -EnvironmentFile=-/etc/sysconfig/rpcbind > -ExecStart=/sbin/rpcbind -w $RPCBIND_OPTIONS > - > -[Install] > -WantedBy=multi-user.target > -Also=rpcbind.socket > diff --git a/rpcbind.socket b/rpcbind.socket > deleted file mode 100644 > index d63c1d9..0000000 > --- a/rpcbind.socket > +++ /dev/null > @@ -1,8 +0,0 @@ > -[Unit] > -Description=RPCbind Server Activation Socket > - > -[Socket] > -ListenStream=/var/run/rpcbind.sock > - > -[Install] > -WantedBy=sockets.target > ================================================================ > > ---- gitweb: > > [5]http://git.pld-linux.org/gitweb.cgi/packages/rpcbind.git/commitdiff/743aa2864 > e361cc9aabb9e1365975d257d2ff599 > > _______________________________________________ > pld-cvs-commit mailing list > [6]pld-cvs-commit at lists.pld-linux.org > [7]http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit > > References > > 1. mailto:qboosh at pld-linux.org > 2. http://downloads.sourceforge.net/rpcbind/% > 3. http://nfsv4.bullopensource.org/doc/tirpc_rpcbind.php > 4. http://sourceforge.net/projects/rpcbind/ > 5. http://git.pld-linux.org/gitweb.cgi/packages/rpcbind.git/commitdiff/743aa2864e361cc9aabb9e1365975d257d2ff599 > 6. mailto:pld-cvs-commit at lists.pld-linux.org > 7. http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit > _______________________________________________ > pld-devel-en mailing list > pld-devel-en at lists.pld-linux.org > http://lists.pld-linux.org/mailman/listinfo/pld-devel-en -- Jakub Bogusz http://qboosh.pl/ From glen at pld-linux.org Thu Jul 19 10:18:42 2018 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=C3=A4e?=) Date: Thu, 19 Jul 2018 11:18:42 +0300 Subject: Fwd: [openssl-announce] Blog post on the new LTS release In-Reply-To: References: Message-ID: ---------- Forwarded message --------- From: Salz, Rich Date: Tue, May 29, 2018 at 6:16 PM Subject: [openssl-announce] Blog post on the new LTS release To: openssl-users , openssl-announce at openssl.org We just posted a new blog entry on long-term support, the different phases, and so on. It?s here: https://www.openssl.org/blog/blog/2018/05/18/new-lts/ TL;DR is that the upcoming 1.1.1 will be our next LTS release. From glen at delfi.ee Fri Jul 20 13:02:02 2018 From: glen at delfi.ee (Elan Ruusamae) Date: Fri, 20 Jul 2018 14:02:02 +0300 Subject: [packages/ruby-ohai] - up to 14.2.0 In-Reply-To: <686e2c781961251823ff8238e66acc5dfa0aa702_refs_heads_master@pld-linux.org> References: <686e2c781961251823ff8238e66acc5dfa0aa702_refs_heads_master@pld-linux.org> Message-ID: why are you not checking other branches. i'm working on this. same for chef, there existed wip branch chef-12 On 7/16/18 10:02 PM, baggins wrote: > commit 686e2c781961251823ff8238e66acc5dfa0aa702 > Author: Jan R?korajski > Date: Mon Jul 16 21:02:13 2018 +0200 > > - up to 14.2.0 > > platform-pld.patch | 19 ++++++++++--------- > ruby-ohai.spec | 12 ++++++------ > soft-net-dhcp.patch | 21 --------------------- > 3 files changed, 16 insertions(+), 36 deletions(-) > --- > diff --git a/ruby-ohai.spec b/ruby-ohai.spec > index 67b8101..1f5fdd4 100644 > --- a/ruby-ohai.spec > +++ b/ruby-ohai.spec > @@ -7,19 +7,20 @@ > %define pkgname ohai > Summary: Profiles your system and emits JSON > Name: ruby-%{pkgname} > -Version: 7.6.0 > -Release: 5 > +Version: 14.2.0 > +Release: 0.1 From baggins at pld-linux.org Fri Jul 20 21:29:57 2018 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Fri, 20 Jul 2018 21:29:57 +0200 Subject: [packages/ruby-ohai] - up to 14.2.0 In-Reply-To: References: <686e2c781961251823ff8238e66acc5dfa0aa702_refs_heads_master@pld-linux.org> Message-ID: <20180720192936.GA14141@tachikoma.lan> On Fri, 20 Jul 2018, Elan Ruusamae wrote: > why are you not checking other branches. i'm working on this. Did you take a look at time and version differences? OTOH, I know it's git and all that, but proliferation of branches is not helping if stuff on head is ancient. commit b5b87a62bc781a13e841b7979c0f34791d687e5b (HEAD -> chef-14, origin/chef-14) Author: Elan Ruusam?e Date: Mon Jul 16 16:13:19 2018 +0300 up to 14.1.7 vs commit 686e2c781961251823ff8238e66acc5dfa0aa702 (HEAD -> master, origin/master) Author: Jan R?korajski Date: Mon Jul 16 21:02:13 2018 +0200 - up to 14.2.0 > same for chef, there existed wip branch chef-12 12 vs 14 -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From glen at delfi.ee Sat Jul 21 17:10:47 2018 From: glen at delfi.ee (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sat, 21 Jul 2018 18:10:47 +0300 Subject: [packages/ruby-ohai] - up to 14.2.0 In-Reply-To: <20180720192936.GA14141@tachikoma.lan> References: <686e2c781961251823ff8238e66acc5dfa0aa702_refs_heads_master@pld-linux.org> <20180720192936.GA14141@tachikoma.lan> Message-ID: <066aa585-06a2-fd8f-c6b9-4dd6b513ae33@delfi.ee> On 20/07/2018 22:29, Jan R?korajski wrote: > On Fri, 20 Jul 2018, Elan Ruusamae wrote: > >> why are you not checking other branches. i'm working on this. > Did you take a look at time and version differences? > > OTOH, I know it's git and all that, but proliferation of branches is not > helping if stuff on head is ancient. that piece software is not easy to update if you actually use chef. that's why i have not updated it for a while. > commit b5b87a62bc781a13e841b7979c0f34791d687e5b (HEAD -> chef-14, origin/chef-14) > Author: Elan Ruusam?e > Date: Mon Jul 16 16:13:19 2018 +0300 > > up to 14.1.7 > > vs > > commit 686e2c781961251823ff8238e66acc5dfa0aa702 (HEAD -> master, origin/master) > Author: Jan R?korajski > Date: Mon Jul 16 21:02:13 2018 +0200 > > - up to 14.2.0 it's using matching version for chef version. just that you able to write .rpm package does not mean the resulting software actually works. the version on master is not usable, don't move it to main. >> same for chef, there existed wip branch chef-12 > 12 vs 14 > yet you think starting from outdated master is better than some other developers hard work to update master to chef-12? it was not merged to master because update was not success From arekm at maven.pl Mon Jul 23 11:15:03 2018 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Mon, 23 Jul 2018 11:15:03 +0200 Subject: [packages/bind] - compact root.hint with root zone NSes only taken from another source; there is no need for such hu In-Reply-To: <065091cf865bc6f8b14417f31729c7a77f641b98_refs_heads_master@pld-linux.org> References: <065091cf865bc6f8b14417f31729c7a77f641b98_refs_heads_master@pld-linux.org> Message-ID: <201807231115.04147.arekm@maven.pl> On Monday 23 of July 2018, adwol wrote: > commit 065091cf865bc6f8b14417f31729c7a77f641b98 > Author: Adam Osuchowski > Date: Mon Jul 23 10:39:28 2018 +0200 > > - compact root.hint with root zone NSes only taken from another source; > there is no need for such huge hint file dnssec records are not needed? -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From adwol at zonk.pl Mon Jul 23 11:49:51 2018 From: adwol at zonk.pl (Adam Osuchowski) Date: Mon, 23 Jul 2018 11:49:51 +0200 Subject: [packages/bind] - compact root.hint with root zone NSes only taken from another source; there is no need for such hu In-Reply-To: <201807231115.04147.arekm@maven.pl> References: <065091cf865bc6f8b14417f31729c7a77f641b98_refs_heads_master@pld-linux.org> <201807231115.04147.arekm@maven.pl> Message-ID: <20180723094951.6b8b4567@zonk.pl> Arkadiusz Mi?kiewicz wrote: > On Monday 23 of July 2018, adwol wrote: > > commit 065091cf865bc6f8b14417f31729c7a77f641b98 > > Author: Adam Osuchowski > > Date: Mon Jul 23 10:39:28 2018 +0200 > > > > - compact root.hint with root zone NSes only taken from another source; > > there is no need for such huge hint file > > dnssec records are not needed? No, they aren't. Root KSK keys, which are anchor of chain of trust, are stored in bind.keys file bundled with bind.