public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] cpio: Update to 2.14
Date: Mon, 08 Jan 2024 06:24:00 +0000	[thread overview]
Message-ID: <a2c1234c-a84d-4ea7-9b82-34f0350e1372@ipfire.org> (raw)

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

Noteworthy changes in this release, according to
https://lists.gnu.org/archive/html/info-gnu/2023-05/msg00001.html :

* New option --ignore-dirnlink

Valid in copy-out mode, it instructs cpio to ignore the actual number
of links reported for each directory member and always store 2
instead.

* Changes in --reproducible option

The --reproducible option implies --ignore-dirlink.  In other words,
it is equivalent to --ignore-devno --ignore-dirnlink --renumber-inodes.

* Use GNU ls algorithm for deciding timestamp format in -tv mode

* Bugfixes

** Fix cpio header verification.

** Fix handling of device numbers on copy out.

** Fix calculation of CRC in copy-out mode.

** Rewrite the fix for CVE-2015-1197.

** Fix combination of --create --append --directory.

** Fix appending to archives bigger than 2G.

Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
---
 config/rootfiles/common/cpio | 1 +
 lfs/cpio                     | 6 +++---
 2 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/config/rootfiles/common/cpio b/config/rootfiles/common/cpio
index 45bf9f79c..7b9bae045 100644
--- a/config/rootfiles/common/cpio
+++ b/config/rootfiles/common/cpio
@@ -12,6 +12,7 @@ bin/cpio
 #usr/share/locale/id/LC_MESSAGES/cpio.mo
 #usr/share/locale/it/LC_MESSAGES/cpio.mo
 #usr/share/locale/ja/LC_MESSAGES/cpio.mo
+#usr/share/locale/ka/LC_MESSAGES/cpio.mo
 #usr/share/locale/ko/LC_MESSAGES/cpio.mo
 #usr/share/locale/nl/LC_MESSAGES/cpio.mo
 #usr/share/locale/pl/LC_MESSAGES/cpio.mo
diff --git a/lfs/cpio b/lfs/cpio
index 6c1e6faa5..f44fe1d2c 100644
--- a/lfs/cpio
+++ b/lfs/cpio
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007-2019  IPFire Team  <info(a)ipfire.org>                     #
+# Copyright (C) 2007-2023  IPFire Team  <info(a)ipfire.org>                     #
 #                                                                             #
 # This program is free software: you can redistribute it and/or modify        #
 # it under the terms of the GNU General Public License as published by        #
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 2.13
+VER        = 2.14
 
 THISAPP    = cpio-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -42,7 +42,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 225f88b7a3e916110671075249217e4811efe767d5c202b420565038a00c2df59159493ac1daefc3ce4349f34c560fcf90b26418f09f05adf7f3b79566ab74de
+$(DL_FILE)_BLAKE2 = ddfecf7e3ff59cb15fa0856d374a8b1ff5aaf9143a940202c6c0eb84f0347b940a40e31258035e1d217fe210ef7ffdedb41e40f3a9d47ba51f44626378090f8a
 
 install : $(TARGET)
 
-- 
2.35.3

                 reply	other threads:[~2024-01-08  6:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=a2c1234c-a84d-4ea7-9b82-34f0350e1372@ipfire.org \
    --to=peter.mueller@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