From: "Lars Wendler" <polynomial-c@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-libs/liburing/files/, sys-libs/liburing/
Date: Thu, 19 Aug 2021 16:27:39 +0000 (UTC) [thread overview]
Message-ID: <1629390452.4d672144f7917d2560fcc053736ab3b001a9675a.polynomial-c@gentoo> (raw)
commit: 4d672144f7917d2560fcc053736ab3b001a9675a
Author: Lars Wendler <polynomial-c <AT> gentoo <DOT> org>
AuthorDate: Thu Aug 19 16:26:27 2021 +0000
Commit: Lars Wendler <polynomial-c <AT> gentoo <DOT> org>
CommitDate: Thu Aug 19 16:27:32 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4d672144
sys-libs/liburing: Revbump to fix version in pkgconfig file
Thanks-to: Florian Schmaus <flow <AT> gentoo.org>
Closes: https://bugs.gentoo.org/809095
Signed-off-by: Lars Wendler <polynomial-c <AT> gentoo.org>
.../liburing/files/liburing-2.0-spec_version.patch | 29 ++++++++++++++++++++++
...{liburing-2.0.ebuild => liburing-2.0-r1.ebuild} | 4 +++
2 files changed, 33 insertions(+)
diff --git a/sys-libs/liburing/files/liburing-2.0-spec_version.patch b/sys-libs/liburing/files/liburing-2.0-spec_version.patch
new file mode 100644
index 00000000000..fab05916c36
--- /dev/null
+++ b/sys-libs/liburing/files/liburing-2.0-spec_version.patch
@@ -0,0 +1,29 @@
+From 1815337f7dbb530ae3e3bc1175d8da214cf76eb5 Mon Sep 17 00:00:00 2001
+From: Stefan Hajnoczi <stefanha@redhat.com>
+Date: Tue, 9 Mar 2021 14:19:12 +0000
+Subject: [PATCH] spec: bump version to 2.0
+
+The shared library is now liburing.so.2 but the pkgconfig and rpm files
+still say 0.7. Existing binaries link against liburing.so.1 and will not
+automatically pick up the new liburing.so.2 shared library.
+
+Update the version number in liburing.spec so
+
+Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
+Link: https://lore.kernel.org/r/20210309141913.262131-2-stefanha@redhat.com
+Signed-off-by: Jens Axboe <axboe@kernel.dk>
+---
+ liburing.spec | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/liburing.spec b/liburing.spec
+index fa4d9704..8607074c 100644
+--- a/liburing.spec
++++ b/liburing.spec
+@@ -1,5 +1,5 @@
+ Name: liburing
+-Version: 0.7
++Version: 2.0
+ Release: 1%{?dist}
+ Summary: Linux-native io_uring I/O access library
+ License: (GPLv2 with exceptions and LGPLv2+) or MIT
diff --git a/sys-libs/liburing/liburing-2.0.ebuild b/sys-libs/liburing/liburing-2.0-r1.ebuild
similarity index 95%
rename from sys-libs/liburing/liburing-2.0.ebuild
rename to sys-libs/liburing/liburing-2.0-r1.ebuild
index 827024e45bc..652b4092a8b 100644
--- a/sys-libs/liburing/liburing-2.0.ebuild
+++ b/sys-libs/liburing/liburing-2.0-r1.ebuild
@@ -21,6 +21,10 @@ IUSE="static-libs"
# fsync test hangs forever
RESTRICT="test"
+PATCHES=(
+ "${FILESDIR}/${P}-spec_version.patch" #809095
+)
+
src_prepare() {
default
multilib_copy_sources
next reply other threads:[~2021-08-19 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 16:27 Lars Wendler [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-19 18:01 [gentoo-commits] repo/gentoo:master commit in: sys-libs/liburing/files/, sys-libs/liburing/ Florian Schmaus
2023-12-16 8:24 Sam James
2023-02-14 9:43 Florian Schmaus
2021-03-12 15:06 Jory Pratt
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=1629390452.4d672144f7917d2560fcc053736ab3b001a9675a.polynomial-c@gentoo \
--to=polynomial-c@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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