public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] aprutil: Update to version 1.6.6
Date: Wed,  4 Nov 2026 14:49:53 +0100	[thread overview]
Message-ID: <20261104135004.2059527-1-adolf.belka@ipfire.org> (raw)

- Update from version 1.6.5 to 1.6.6
- Update of rootfile
- Although there are only two line entries in the changelog another part of the website
   says "The main changes in this release are concerned with the third-party
   dependencies, including unbundling expat, and building with up-to-date versions of
   libraries such as OpenSSL and MySQL."
- So the recommendation is to upgrade and hence I have provided this patch submission.
   However, as far as I can tell we have explicitly told the configure to use expat and
   openssl that we have built in IPFire and not to use the bundled packages so it may not
   make any difference for us.
- Changelog
1.6.6
  *) Fix crypto/apr_passwd.c compilation errors on older systems. PR 70283.
  *) Fix crashes in apr_crypto_get_block_key_types() with default cmake builds on
     Windows. PR 70260.

Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
 config/rootfiles/common/aprutil | 2 +-
 lfs/aprutil                     | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/config/rootfiles/common/aprutil b/config/rootfiles/common/aprutil
index 672c5a692..44e1bb55e 100644
--- a/config/rootfiles/common/aprutil
+++ b/config/rootfiles/common/aprutil
@@ -48,5 +48,5 @@ usr/lib/apr-util-1/apr_dbm_gdbm.so
 #usr/lib/libaprutil-1.la
 #usr/lib/libaprutil-1.so
 usr/lib/libaprutil-1.so.0
-usr/lib/libaprutil-1.so.0.6.5
+usr/lib/libaprutil-1.so.0.6.6
 #usr/lib/pkgconfig/apr-util-1.pc
diff --git a/lfs/aprutil b/lfs/aprutil
index 39761715c..fb06aad4e 100644
--- a/lfs/aprutil
+++ b/lfs/aprutil
@@ -25,7 +25,7 @@
 
 include Config
 
-VER        = 1.6.5
+VER        = 1.6.6
 
 THISAPP    = apr-util-$(VER)
 DL_FILE    = $(THISAPP).tar.bz2
@@ -44,7 +44,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = ee11e45f0029b336c80536f0b98b48f044229d5b9d8669471a1f0641eee8aa6ddbd8f2249ce6116294dc3d3c5b8b939532c366e6208dafe325eeba1db2603300
+$(DL_FILE)_BLAKE2 = b4062cbdf8ef9ba1f83879695eb16fb7344760c0c1642365353f2c225bb3fc2fbb6389fd08edb594d7c6fa62492735045d652db969e52262994830e70e3e92dc
 
 install : $(TARGET)
 
-- 
2.56.0



             reply	other threads:[~2026-11-04 13:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 13:49 Adolf Belka [this message]
2026-11-04 13:49 ` [PATCH] core207: Ship aprutil Adolf Belka
2026-11-04 13:49 ` [PATCH] core207: Ship fribidi Adolf Belka
2026-11-04 13:49 ` [PATCH] core207: Ship kmod Adolf Belka
2026-11-04 13:49 ` [PATCH] core207: Ship libjpeg Adolf Belka
2026-11-04 13:49 ` [PATCH] core207: Ship nano Adolf Belka
2026-11-04 13:49 ` [PATCH] fribidi: Update to version 1.0.18 Adolf Belka
2026-11-04 13:50 ` [PATCH] kmod: Update to version 34.3 Adolf Belka
2026-11-04 13:50 ` [PATCH] libarchive: Update to version 3.8.11 Adolf Belka
2026-11-04 13:50 ` [PATCH] libjpeg: Update to version 3.2.1 Adolf Belka
2026-11-04 13:50 ` [PATCH] nano: Update to version 9.3 Adolf Belka

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=20261104135004.2059527-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