From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] dnf: upgrade 4.9.0 -> 4.10.0
Date: Mon, 25 Oct 2021 22:26:53 +0800 [thread overview]
Message-ID: <1635172017-18309-2-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1635172017-18309-1-git-send-email-wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
meta/recipes-devtools/dnf/{dnf_4.9.0.bb => dnf_4.10.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/dnf/{dnf_4.9.0.bb => dnf_4.10.0.bb} (98%)
diff --git a/meta/recipes-devtools/dnf/dnf_4.9.0.bb b/meta/recipes-devtools/dnf/dnf_4.10.0.bb
similarity index 98%
rename from meta/recipes-devtools/dnf/dnf_4.9.0.bb
rename to meta/recipes-devtools/dnf/dnf_4.10.0.bb
index 27df88342e..b7273d4051 100644
--- a/meta/recipes-devtools/dnf/dnf_4.9.0.bb
+++ b/meta/recipes-devtools/dnf/dnf_4.10.0.bb
@@ -18,7 +18,7 @@ SRC_URI = "git://github.com/rpm-software-management/dnf.git \
file://0001-dnf-write-the-log-lock-to-root.patch \
"
-SRCREV = "f85cf31395156a2aa5d75e894e5794a771054fe4"
+SRCREV = "bd691b784f2158e633072d368579898d740e4347"
UPSTREAM_CHECK_GITTAGREGEX = "(?P<pver>\d+(\.\d+)+)"
S = "${WORKDIR}/git"
--
2.25.1
next prev parent reply other threads:[~2021-10-25 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 14:26 [OE-core] [PATCH] dhcpcd: upgrade 9.4.0 -> 9.4.1 Wang Mingyu
2021-10-25 14:26 ` Wang Mingyu [this message]
2021-10-25 14:26 ` [OE-core] [PATCH] file: upgrade 5.40 -> 5.41 Wang Mingyu
2021-10-25 14:26 ` [OE-core] [PATCH] libdnf: upgrade 0.64.0 -> 0.65.0 Wang Mingyu
2021-10-25 14:26 ` [OE-core] [PATCH] lttng-tools: upgrade 2.13.0 -> 2.13.1 Wang Mingyu
2021-10-25 18:28 ` Alexandre Belloni
2021-10-25 18:52 ` Khem Raj
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=1635172017-18309-2-git-send-email-wangmy@fujitsu.com \
--to=wangmy@fujitsu.com \
--cc=openembedded-core@lists.openembedded.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