From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. dc9f7554c13ebdadb45f27c8f38f14b9d16468d2
Date: Fri, 02 Dec 2022 16:43:40 +0000 [thread overview]
Message-ID: <4NNzKS6qllz2xPL@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1679 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via dc9f7554c13ebdadb45f27c8f38f14b9d16468d2 (commit)
from a3e3e6c3d1c61e59f83aebc030e430014b10a796 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit dc9f7554c13ebdadb45f27c8f38f14b9d16468d2
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Fri Dec 2 17:43:04 2022 +0100
Core Update 172: Zut alors, keep libhistory.so.8.1 around as well
My fault, again. :-/
Reported-by: Adolf Belka <adolf.belka(a)ipfire.org>
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/172/update.sh | 1 -
1 file changed, 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/172/update.sh b/config/rootfiles/core/172/update.sh
index a2292b7ae..4752b4cc8 100644
--- a/config/rootfiles/core/172/update.sh
+++ b/config/rootfiles/core/172/update.sh
@@ -77,7 +77,6 @@ rm -rvf \
/usr/lib/libdns-9.16.33.so \
/usr/lib/libedit.so.0.0.6* \
/usr/lib/libexpat.so.1.8.9 \
- /usr/lib/libhistory.so.8.1 \
/usr/lib/libirs-9.16.33.so \
/usr/lib/libisc-9.16.33.so \
/usr/lib/libisccc-9.16.33.so \
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-12-02 16:43 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=4NNzKS6qllz2xPL@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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