From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] netatalk: Ship with CU169 - Fixes bug #12878
Date: Thu, 16 Jun 2022 23:16:36 +0200 [thread overview]
Message-ID: <20220616211636.2812067-1-adolf.belka@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
- netatalk is linked to liblber from openldap. openldap was updated in CU168 but
I missed that netatalk had a dependency to one of its libraries.
- find-dependencies was not run on openldap liblber although looking at the openldap
rootfile it is clear that an sobump occurred.
- This patch increments the netatalk PAK_VER so that it will be shipped and therefore
have the library links updated.
Fixes: Bug #12878
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
lfs/netatalk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lfs/netatalk b/lfs/netatalk
index 61ba193a5..9e8ce454b 100644
--- a/lfs/netatalk
+++ b/lfs/netatalk
@@ -34,7 +34,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = netatalk
-PAK_VER = 2
+PAK_VER = 3
DEPS = avahi dbus krb5
--
2.36.1
next reply other threads:[~2022-06-16 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 21:16 Adolf Belka [this message]
2022-06-17 8:46 ` Peter Müller
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=20220616211636.2812067-1-adolf.belka@ipfire.org \
--to=adolf.belka@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