public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Wolfgang Apolinarski <wolfgang@apolinarski.de>
To: development@lists.ipfire.org
Subject: Unbound - rootfile
Date: Sun, 18 Jun 2017 17:06:01 +0200	[thread overview]
Message-ID: <000001d2e844$66115dc0$32341940$@apolinarski.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 939 bytes --]

Hi everyone,

while trying to create a nice patch for the next patch-merge-window, I was
encountering an error that preventing the proper execution of "./make.sh
build".

Apparently the unbound update did not get a rootfile update. After changing
it, it worked fine (patch, see below).

Nevertheless, I still get warnings about the rootfiles of kbd, unbound and
cmake (and no, my patch does not change them).

Best regards,
Wolfgang
PS.: I'm currently testing everything on a fresh install of CentOS, to
mitigate side-effects from previous builds.
PPS.: You are not using a build server system of some kind, right?

--- a/config/rootfiles/common/unbound
+++ b/config/rootfiles/common/unbound
@@ -11,7 +11,7 @@ etc/unbound/unbound.conf
 #usr/lib/libunbound.la
 #usr/lib/libunbound.so
 usr/lib/libunbound.so.2
-usr/lib/libunbound.so.2.5.1
+usr/lib/libunbound.so.2.5.2
 usr/sbin/unbound
 usr/sbin/unbound-anchor
 usr/sbin/unbound-checkconf



             reply	other threads:[~2017-06-18 15:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-18 15:06 Wolfgang Apolinarski [this message]
2017-06-18 16:38 ` Michael Tremer
2017-06-29 10:06 ` FYI: Systemd CVE 2017-9445 5p9
2017-06-29 10:37   ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000001d2e844$66115dc0$32341940$@apolinarski.de' \
    --to=wolfgang@apolinarski.de \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox