From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 3757d24e470975ab3451a1d8adb36281468c0532
Date: Wed, 07 Feb 2024 11:22:35 +0000 [thread overview]
Message-ID: <4TVHlb34wZz2xGY@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1611 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 3757d24e470975ab3451a1d8adb36281468c0532 (commit)
from b8c898b4824624b802ffda8b92c7009ea5a9db46 (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 3757d24e470975ab3451a1d8adb36281468c0532
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Feb 7 11:21:49 2024 +0000
libvirt: Don't build for riscv64
There seems to be some problem that this package does not build from
source, but as we don't currently have any hardware that supports thise,
there is no point in debugging it.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/libvirt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/libvirt b/lfs/libvirt
index 3035844f0..ef122cfa7 100644
--- a/lfs/libvirt
+++ b/lfs/libvirt
@@ -33,7 +33,7 @@ DL_FILE = $(THISAPP).tar.xz
DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
-# SUP_ARCH = x86_64 aarch64
+SUP_ARCH = x86_64 aarch64
PROG = libvirt
PAK_VER = 34
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-02-07 11:22 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=4TVHlb34wZz2xGY@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