public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] libcap: Update to version 2.73
Date: Sat, 14 Dec 2024 12:08:48 +0000	[thread overview]
Message-ID: <2EDFF517-7AD7-4B61-B501-6531C09DEAEE@ipfire.org> (raw)
In-Reply-To: <20241213190034.3426507-1-adolf.belka@ipfire.org>

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

Thank you. Merged.

> On 13 Dec 2024, at 19:00, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> - Update from version 2.72 to 2.73
> - Update of rootfile
> - This version builds correctly with aarch64 - tested out building on the aarch64-builder
>   system
> - Changelog
>    2.73
> Bug fixes for libpsx changes in the 2.72 release.
>    Some architectures do not support the system call getdents(). More
>     modern architectures only support getdents64(), so use that. Patch
>     provided by Xi Ruoyao.
>    gettid() isn't consistently defined in all *libc's so create a macro
>     for using it in the libpsx sources.
> Fix some static analysis found issues, surfaced by Carlos
> Rodriguez-Fernandez from an analysis performed on Fedora's libcap-2.71
> release.
> Third attempt to get an executable cap package runnable example into the
> documentation on go.pkg.dev.
>    It still isn't working, but I think the issue is now one for the go.dev
>     website:
>    Filed go/issues/70630 which got duped into this go/issues/70611 and
>     a fix was requested by Ian Taylor.
>    Remove a redundant c.String() function since fmt.Println(c) can figure
>     this detail out.
> Freshen up setcap.c sources. Sort the argument help.
> Add go vet to the tests for cap and psx packages.
> 
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> config/rootfiles/common/libcap | 4 ++--
> lfs/libcap                     | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/config/rootfiles/common/libcap b/config/rootfiles/common/libcap
> index 82754304e..dc411f3e5 100644
> --- a/config/rootfiles/common/libcap
> +++ b/config/rootfiles/common/libcap
> @@ -6,10 +6,10 @@ sbin/setcap
> #usr/include/sys/psx_syscall.h
> #usr/lib/libcap.so
> usr/lib/libcap.so.2
> -usr/lib/libcap.so.2.72
> +usr/lib/libcap.so.2.73
> #usr/lib/libpsx.so
> #usr/lib/libpsx.so.2
> -usr/lib/libpsx.so.2.72
> +usr/lib/libpsx.so.2.73
> #usr/lib/pkgconfig/libcap.pc
> #usr/lib/pkgconfig/libpsx.pc
> #usr/lib/security
> diff --git a/lfs/libcap b/lfs/libcap
> index c4a50b2c7..99fd26bb7 100644
> --- a/lfs/libcap
> +++ b/lfs/libcap
> @@ -24,7 +24,7 @@
> 
> include Config
> 
> -VER        = 2.72
> +VER        = 2.73
> 
> THISAPP    = libcap-$(VER)
> DL_FILE    = $(THISAPP).tar.xz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
> 
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> 
> -$(DL_FILE)_BLAKE2 = 2c854fd9a714ab1daae3831829b4b7a890a0894953ba88ae1e190274e7fc635275ce4bf2c668b390ba8196248cb1f953fafb3a9af3907e688c1ab40774f7c6e0
> +$(DL_FILE)_BLAKE2 = c8ea9b8accc4034adfd31295ec9356dcce3ae46b3e532e089248c20d0f148de17c9a0525e9f15ac839f83351cdff9e0f9e91ee8966c34116ad1411917f9358b2
> 
> install : $(TARGET)
> 
> -- 
> 2.47.1
> 


      reply	other threads:[~2024-12-14 12:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13 19:00 Adolf Belka
2024-12-14 12:08 ` Michael Tremer [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=2EDFF517-7AD7-4B61-B501-6531C09DEAEE@ipfire.org \
    --to=michael.tremer@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