public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowi@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/libkrun] rawhide: Update RPM macro dependency
Date: Mon, 24 Aug 2026 14:36:38 GMT [thread overview]
Message-ID: <178758219856.1.5961459520884241222.rpms-libkrun-34982045aa28@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/libkrun
Branch : rawhide
Commit : 34982045aa287261a97d76602eac0c4d98ee14b9
Author : Yaakov Selkowitz <yselkowi@redhat.com>
Date : 2026-08-10T23:08:08-04:00
Stats : +8/-4 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/libkrun/c/34982045aa287261a97d76602eac0c4d98ee14b9?branch=rawhide
Log:
Update RPM macro dependency
---
diff --git a/libkrun.spec b/libkrun.spec
index 25b07b1..58b5e98 100644
--- a/libkrun.spec
+++ b/libkrun.spec
@@ -55,12 +55,16 @@ Requires: libkrunfw >= 5.0.0
# file that also needs to be compiled, and the resulting binary a dynamic
# library providing a C-compatible ABI.
#
-# As a result, we can't fully rely on rust-packaging for managing this package.
+# As a result, we can't fully rely on cargo-rpm-macros for managing this package.
# Instead, we use some of its tasks (cargo_prep and cargo_test) and combine
# them with using the Makefile provided by the project. We also need to manage
-# BuildRequires manually, as rust-packaging gets confused trying to generate
-# them dynamically.
-BuildRequires: rust-packaging >= 21
+# BuildRequires manually, as cargo_generate_buildrequires gets confused trying
+# to generate them dynamically.
+%if 0%{?rhel}
+BuildRequires: rust-toolset
+%else
+BuildRequires: cargo-rpm-macros
+%endif
BuildRequires: glibc-static
BuildRequires: binutils
BuildRequires: libcap-ng-devel
reply other threads:[~2026-08-24 14:36 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=178758219856.1.5961459520884241222.rpms-libkrun-34982045aa28@fedoraproject.org \
--to=yselkowi@redhat.com \
--cc=git-commits@fedoraproject.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