From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] unbound: Update to 1.21.0
Date: Fri, 16 Aug 2024 17:32:06 +0200 [thread overview]
Message-ID: <73ca5432-1a57-4818-833a-8129cbba24ce@ipfire.org> (raw)
In-Reply-To: <7777D66A-4ED9-46EF-89BC-50D08137C146@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2371 bytes --]
On 16.08.2024 14:46, Michael Tremer wrote:
> Hello Matthias,
Hi Michael,
> Thanks for the patch. I assume that your build environment is running smooth again?
As I wrote earlier: this patch - who somehow made it into patchwork (not
Applicable!) - fixed it for me:
https://patchwork.ipfire.org/project/ipfire/patch/8ad8b53e-0e31-4059-87d4-b3c08ab3d7e7(a)ipfire.org/
I just added two lines - don't ask me why...but the Devels are building
'next' again... ;-)
>> On 15 Aug 2024, at 21:57, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>
>> For details see:
>> https://nlnetlabs.nl/projects/unbound/download/#unbound-1-21-0
>>
>> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
>> ---
>> config/rootfiles/common/unbound | 3 ++-
>> lfs/unbound | 4 ++--
>> 2 files changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/config/rootfiles/common/unbound b/config/rootfiles/common/unbound
>> index ca50dd984..03e382d2e 100644
>> --- a/config/rootfiles/common/unbound
>> +++ b/config/rootfiles/common/unbound
>> @@ -10,7 +10,8 @@ etc/unbound/unbound.conf
>> #usr/include/unbound.h
>> #usr/lib/libunbound.la
>> #usr/lib/libunbound.so
>> -usr/lib/libunbound.so.8.1.27
>> +usr/lib/libunbound.so.8
>> +usr/lib/libunbound.so.8.1.28
>> #usr/lib/pkgconfig/libunbound.pc
>> usr/sbin/unbound
>> usr/sbin/unbound-anchor
>
> For some reason, this part did not apply, because the .so.8 file was there before. I fixes this for you.
Ups. I don't know how this happened - thanks anyway! ;-)
Best
Matthias
> -Michael
>
>> diff --git a/lfs/unbound b/lfs/unbound
>> index 580508809..f10fed82d 100644
>> --- a/lfs/unbound
>> +++ b/lfs/unbound
>> @@ -24,7 +24,7 @@
>>
>> include Config
>>
>> -VER = 1.20.0
>> +VER = 1.21.0
>>
>> THISAPP = unbound-$(VER)
>> DL_FILE = $(THISAPP).tar.gz
>> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>>
>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>
>> -$(DL_FILE)_BLAKE2 = b272a6b8c0118819d9803f0c7f7a4b7eff77e37682f4a9a0f749cafa08da4d4de01cd7bf71698b8fc5a7cdf5ca03685978e6b4395c586c35d1d13bebb7cbb538
>> +$(DL_FILE)_BLAKE2 = f6dc7b60e0071d3a7e7e687eb76fd086590ac69da954775c85bd09d8caa5e0cc4181c97fc14a75d2235f3b182d2d5b0b9120e453beb4e112af67ac80216cfca9
>>
>> install : $(TARGET)
>>
>> --
>> 2.34.1
>>
>
prev parent reply other threads:[~2024-08-16 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 20:57 Matthias Fischer
2024-08-16 12:46 ` Michael Tremer
2024-08-16 15:32 ` Matthias Fischer [this message]
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=73ca5432-1a57-4818-833a-8129cbba24ce@ipfire.org \
--to=matthias.fischer@ipfire.org \
--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