From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 01/15] libcap: Update to version 2.70
Date: Fri, 09 Aug 2024 17:14:01 +0200 [thread overview]
Message-ID: <c8bc74ec-b32d-4e68-949a-456dd821fd12@ipfire.org> (raw)
In-Reply-To: <D3AD0330-BA4B-4375-8011-C5EFC068DFA9@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 4325 bytes --]
Hi Michael,
On 09/08/2024 16:23, Michael Tremer wrote:
> Hello,
>
> I don’t think we have an SO bump here…
When I look at it now, it doesn't look like an sobump but clearly for some reason I thought it was.
Oh well, then all those additional patches for the addons can be thrown away.
Looking below in the rootfile I do see that libpsx.so.2 is commented out. Should that be uncommented?
Apologies for the mistake.
Regards,
Adolf.
>
> Binaries should be linked against libcap.2 and that has not changed.
>
> Are they not working with the new version any more?
>
> Best,
> -Michael
>
>> On 9 Aug 2024, at 12:23, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> - Update from version 2.69 to 2.70
>> - Update of rootfile
>> - sobump means following core packages need to be shipped
>> arping
>> cdrkit
>> iproute2
>> iputils
>> ntp
>> squid
>> udev
>> and the following addons will be shipped with the pak_ver increments in the other
>> patches that are part ofg this set
>> avahi
>> bacula
>> cifs-utils
>> dnsdist
>> freeradius
>> frr
>> htop
>> nfs
>> rng-tools
>> samba
>> tor
>> tshark
>> vdr
>> wavemon
>> - Changelog
>> 2.70
>> setcap changes to make it harder to set invalid file capabilities (Bug 217592\
>> reported by parke.nexus)
>> Lots of documentation fixes (contributions from Jakub Wilk and
>> Carlos Rodriguez-Fernandez)
>> Fix c89 compilation syntax for the C code in the libraries.
>> libpam has deprecated providing the _pam_overwrite() function, so use memset()
>> instead
>>
>> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
>> ---
>> config/rootfiles/common/libcap | 8 +++++---
>> lfs/libcap | 6 +++---
>> 2 files changed, 8 insertions(+), 6 deletions(-)
>>
>> diff --git a/config/rootfiles/common/libcap b/config/rootfiles/common/libcap
>> index f331e2a43..ea90c7564 100644
>> --- a/config/rootfiles/common/libcap
>> +++ b/config/rootfiles/common/libcap
>> @@ -4,12 +4,12 @@ sbin/getpcaps
>> sbin/setcap
>> #usr/include/sys/capability.h
>> #usr/include/sys/psx_syscall.h
>> -usr/lib/libcap.so
>> +#usr/lib/libcap.so
>> usr/lib/libcap.so.2
>> -usr/lib/libcap.so.2.69
>> +usr/lib/libcap.so.2.70
>> #usr/lib/libpsx.so
>> #usr/lib/libpsx.so.2
>> -usr/lib/libpsx.so.2.69
>> +usr/lib/libpsx.so.2.70
>> #usr/lib/pkgconfig/libcap.pc
>> #usr/lib/pkgconfig/libpsx.pc
>> #usr/lib/security
>> @@ -88,7 +88,9 @@ usr/lib/security/pam_cap.so
>> #usr/share/man/man3/psx_syscall.3
>> #usr/share/man/man3/psx_syscall3.3
>> #usr/share/man/man3/psx_syscall6.3
>> +#usr/share/man/man5/capability.conf.5
>> #usr/share/man/man8/captree.8
>> #usr/share/man/man8/getcap.8
>> #usr/share/man/man8/getpcaps.8
>> +#usr/share/man/man8/pam_cap.8
>> #usr/share/man/man8/setcap.8
>> diff --git a/lfs/libcap b/lfs/libcap
>> index 951ed80dc..51e32f9c6 100644
>> --- a/lfs/libcap
>> +++ b/lfs/libcap
>> @@ -1,7 +1,7 @@
>> ###############################################################################
>> # #
>> # IPFire.org - A linux based firewall #
>> -# Copyright (C) 2007-2023 IPFire Team <info(a)ipfire.org> #
>> +# Copyright (C) 2007-2024 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.69
>> +VER = 2.70
>>
>> THISAPP = libcap-$(VER)
>> DL_FILE = $(THISAPP).tar.xz
>> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>>
>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>
>> -$(DL_FILE)_BLAKE2 = 94d1fef7666a1c383a8b96f1f6092bd242164631532868b628d2f5de71b42a371d041a978ef7fbadfee3eeb433165444995d1078cd790275bc0433a7875a697e
>> +$(DL_FILE)_BLAKE2 = 77b72acee53032117ea481e3380d1b497f9264b6193b9523542508c7c3e46070248ca4ed910d35809ce6e52caa60cbb31edb125c47221627eeda35c61bd0914b
>>
>> install : $(TARGET)
>>
>> --
>> 2.45.2
>>
>
next prev parent reply other threads:[~2024-08-09 15:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 11:23 Adolf Belka
2024-08-09 11:23 ` [PATCH 02/15] avahi: ship due to libcap sobump Adolf Belka
2024-08-09 11:23 ` [PATCH 03/15] bacula: " Adolf Belka
2024-08-09 11:23 ` [PATCH 04/15] cifs-utils: " Adolf Belka
2024-08-09 11:23 ` [PATCH 05/15] dnsdist: " Adolf Belka
2024-08-09 11:23 ` [PATCH 06/15] freeradius: " Adolf Belka
2024-08-09 11:23 ` [PATCH 07/15] frr: " Adolf Belka
2024-08-09 11:23 ` [PATCH 08/15] htop: " Adolf Belka
2024-08-09 11:23 ` [PATCH 09/15] nfs: " Adolf Belka
2024-08-09 11:23 ` [PATCH 10/15] rng-tools: " Adolf Belka
2024-08-09 11:23 ` [PATCH 11/15] samba: " Adolf Belka
2024-08-09 11:23 ` [PATCH 12/15] tor: " Adolf Belka
2024-08-09 11:23 ` [PATCH 13/15] tshark: " Adolf Belka
2024-08-09 11:23 ` [PATCH 14/15] vdr: " Adolf Belka
2024-08-09 11:23 ` [PATCH 15/15] wavemon: " Adolf Belka
2024-08-09 14:23 ` [PATCH 01/15] libcap: Update to version 2.70 Michael Tremer
2024-08-09 15:14 ` Adolf Belka [this message]
2024-08-13 9:58 ` Michael Tremer
2024-08-13 11:09 ` 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=c8bc74ec-b32d-4e68-949a-456dd821fd12@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