From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. a3e3e6c3d1c61e59f83aebc030e430014b10a796
Date: Fri, 02 Dec 2022 08:58:40 +0000 [thread overview]
Message-ID: <4NNn0w3btlz2xD5@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1844 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, master has been updated
via a3e3e6c3d1c61e59f83aebc030e430014b10a796 (commit)
from 509bde09ae1277a948d18605bd51fd01e5a5bf2b (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 a3e3e6c3d1c61e59f83aebc030e430014b10a796
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Fri Dec 2 09:56:49 2022 +0100
Core Update 172: Do not delete libreadline.so.8.1
Doing so causes the shell in which the update script is currently
executed to crash before extracting files, which results in a
completely broken system.
See also: https://community.ipfire.org/t/core-172-testing-fails/9002/1
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 ecf439a92..a2292b7ae 100644
--- a/config/rootfiles/core/172/update.sh
+++ b/config/rootfiles/core/172/update.sh
@@ -89,7 +89,6 @@ rm -rvf \
/usr/lib/libpoppler-cpp.so.0.9* \
/usr/lib/libpoppler-glib.so.8.23.0 \
/usr/lib/libpoppler.so.120* \
- /usr/lib/libreadline.so.8.1 \
/usr/lib/libtasn1.so.6.6.2 \
/usr/lib/libtiff.so.5.7* \
/usr/lib/libtiffxx.so.5.7* \
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-12-02 8:58 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=4NNn0w3btlz2xD5@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