public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] libcap: Update to version 2.63
Date: Sat, 05 Feb 2022 13:01:10 +0100	[thread overview]
Message-ID: <20220205120110.3445292-1-adolf.belka@ipfire.org> (raw)

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

- Update from 2.61 to 2.63
- Update of rootfile
- Changelog
   Release notes for 2.63
    Restore errno to zero by the time main() is executed
        Bug reported by Yang Xu
    Consistent psx handling (a panic) for syscalls that return thread dependent status
        Inconsistend behavior noticed by Lorenz Bauer (Bug: 215283)
    Add a test case for a deadlock under investigation in golang #50113
        Bug reported by Weixiao Huang
    Trim some of the #include file use to make the tree compile more efficiently
   Release notes for 2.62
    Bug fix for Go package "cap" and launching:
        There was a race condition, reported by Lorenz Bauer (Bug: 215283)
    Build cleanups:
        David Seifert cleaned up warnings for 32-bit builds
        No longer use Perl in the libcap build process (Gentoo had a compelling reason to
         avoid this dependency)
    Documentation updates: cap_max_bits has a man page entry; Go module cap updates for
     Launch detail.
    Recognize default securebits as a libcap mode: HYBRID.

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

diff --git a/config/rootfiles/common/libcap b/config/rootfiles/common/libcap
index c33222c49..0c57c9120 100644
--- a/config/rootfiles/common/libcap
+++ b/config/rootfiles/common/libcap
@@ -1,10 +1,10 @@
 #lib/libcap.a
 lib/libcap.so.2
-lib/libcap.so.2.61
+lib/libcap.so.2.63
 #lib/libpsx.a
 #lib/libpsx.so
 #lib/libpsx.so.2
-#lib/libpsx.so.2.61
+#lib/libpsx.so.2.63
 #lib/pkgconfig/libcap.pc
 #lib/pkgconfig/libpsx.pc
 lib/security/pam_cap.so
@@ -57,6 +57,7 @@ usr/lib/libcap.so
 #usr/share/man/man3/cap_launcher_set_mode.3
 #usr/share/man/man3/cap_launcher_setgroups.3
 #usr/share/man/man3/cap_launcher_setuid.3
+#usr/share/man/man3/cap_max_bits.3
 #usr/share/man/man3/cap_mode.3
 #usr/share/man/man3/cap_mode_name.3
 #usr/share/man/man3/cap_new_launcher.3
@@ -75,6 +76,7 @@ usr/lib/libcap.so
 #usr/share/man/man3/capsetp.3
 #usr/share/man/man3/libcap.3
 #usr/share/man/man3/libpsx.3
+#usr/share/man/man3/psx_set_sensitivity.3
 #usr/share/man/man3/psx_syscall.3
 #usr/share/man/man3/psx_syscall3.3
 #usr/share/man/man3/psx_syscall6.3
diff --git a/lfs/libcap b/lfs/libcap
index 387d43e38..63467062f 100644
--- a/lfs/libcap
+++ b/lfs/libcap
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 2.61
+VER        = 2.63
 
 THISAPP    = libcap-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_MD5 = 3bf105e47a8671035a0ce0812185c5e4
+$(DL_FILE)_MD5 = 18410cec436f827e698ee9ea16ada9b7
 
 install : $(TARGET)
 
-- 
2.35.1


             reply	other threads:[~2022-02-05 12:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-05 12:01 Adolf Belka [this message]
2022-02-05 13:20 ` 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=20220205120110.3445292-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