From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 9c6fd77927cbbf1cedb5d8a0dbc1367b7af17198
Date: Fri, 30 Oct 2020 16:29:58 +0000 [thread overview]
Message-ID: <4CN77p3RyRz2xl6@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2467 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 9c6fd77927cbbf1cedb5d8a0dbc1367b7af17198 (commit)
via 62efd2e9d26b78fe83b850dc43a9206556a2d851 (commit)
from 7f5d63c9e661d8d9feab2723944dc04739205b4b (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 9c6fd77927cbbf1cedb5d8a0dbc1367b7af17198
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Oct 30 16:29:39 2020 +0000
core153: Ship libarchive
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
commit 62efd2e9d26b78fe83b850dc43a9206556a2d851
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Oct 30 16:29:02 2020 +0000
libarchive: Ship on core system
Some tools link against this
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/libarchive | 4 ++--
config/rootfiles/{oldcore/104 => core/153}/filelists/libarchive | 0
2 files changed, 2 insertions(+), 2 deletions(-)
copy config/rootfiles/{oldcore/104 => core/153}/filelists/libarchive (100%)
Difference in files:
diff --git a/config/rootfiles/common/libarchive b/config/rootfiles/common/libarchive
index 10950c9fc..a4038b13f 100644
--- a/config/rootfiles/common/libarchive
+++ b/config/rootfiles/common/libarchive
@@ -5,8 +5,8 @@
#usr/include/archive_entry.h
#usr/lib/libarchive.la
#usr/lib/libarchive.so
-#usr/lib/libarchive.so.13
-#usr/lib/libarchive.so.13.4.0
+usr/lib/libarchive.so.13
+usr/lib/libarchive.so.13.4.0
#usr/lib/pkgconfig/libarchive.pc
#usr/share/man/man1/bsdcat.1
#usr/share/man/man1/bsdcpio.1
diff --git a/config/rootfiles/core/153/filelists/libarchive b/config/rootfiles/core/153/filelists/libarchive
new file mode 120000
index 000000000..551f1f743
--- /dev/null
+++ b/config/rootfiles/core/153/filelists/libarchive
@@ -0,0 +1 @@
+../../../common/libarchive
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-10-30 16:29 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=4CN77p3RyRz2xl6@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