From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 419aaf916cb71e413fe4da76624b90e902b91983
Date: Sun, 13 Feb 2022 08:56:05 +0000 [thread overview]
Message-ID: <4JxLmj2Sv2z2xjC@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2963 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 419aaf916cb71e413fe4da76624b90e902b91983 (commit)
from 5462658ea03ea86d5c093de3eb708d367aa077ac (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 419aaf916cb71e413fe4da76624b90e902b91983
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Feb 13 08:55:24 2022 +0000
libvirt: ship arm cpu configfiles
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/packages/libvirt | 20 ++++++++++----------
lfs/libvirt | 2 +-
2 files changed, 11 insertions(+), 11 deletions(-)
Difference in files:
diff --git a/config/rootfiles/packages/libvirt b/config/rootfiles/packages/libvirt
index b6f639901..e57ead069 100644
--- a/config/rootfiles/packages/libvirt
+++ b/config/rootfiles/packages/libvirt
@@ -206,16 +206,16 @@ usr/sbin/virtstoraged
#usr/share/doc/libvirt/examples/xml/test/testvol.xml
#usr/share/libvirt
#usr/share/libvirt/cpu_map
-#usr/share/libvirt/cpu_map/arm_FT-2000plus.xml
-#usr/share/libvirt/cpu_map/arm_Falkor.xml
-#usr/share/libvirt/cpu_map/arm_Kunpeng-920.xml
-#usr/share/libvirt/cpu_map/arm_Tengyun-S2500.xml
-#usr/share/libvirt/cpu_map/arm_ThunderX299xx.xml
-#usr/share/libvirt/cpu_map/arm_cortex-a53.xml
-#usr/share/libvirt/cpu_map/arm_cortex-a57.xml
-#usr/share/libvirt/cpu_map/arm_cortex-a72.xml
-#usr/share/libvirt/cpu_map/arm_features.xml
-#usr/share/libvirt/cpu_map/arm_vendors.xml
+usr/share/libvirt/cpu_map/arm_FT-2000plus.xml
+usr/share/libvirt/cpu_map/arm_Falkor.xml
+usr/share/libvirt/cpu_map/arm_Kunpeng-920.xml
+usr/share/libvirt/cpu_map/arm_Tengyun-S2500.xml
+usr/share/libvirt/cpu_map/arm_ThunderX299xx.xml
+usr/share/libvirt/cpu_map/arm_cortex-a53.xml
+usr/share/libvirt/cpu_map/arm_cortex-a57.xml
+usr/share/libvirt/cpu_map/arm_cortex-a72.xml
+usr/share/libvirt/cpu_map/arm_features.xml
+usr/share/libvirt/cpu_map/arm_vendors.xml
usr/share/libvirt/cpu_map/index.xml
usr/share/libvirt/cpu_map/ppc64_POWER6.xml
usr/share/libvirt/cpu_map/ppc64_POWER7.xml
diff --git a/lfs/libvirt b/lfs/libvirt
index bc0dfc036..4409fe4e5 100644
--- a/lfs/libvirt
+++ b/lfs/libvirt
@@ -33,7 +33,7 @@ DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
SUP_ARCH = x86_64 aarch64
PROG = libvirt
-PAK_VER = 27
+PAK_VER = 28
DEPS = ebtables libpciaccess libtirpc libyajl ncat qemu
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-02-13 8:56 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=4JxLmj2Sv2z2xjC@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