From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-libs/libnvme/
Date: Tue, 6 Feb 2024 03:05:10 +0000 (UTC) [thread overview]
Message-ID: <1707188614.27f17b985f46015bd296d11976cac73e11532655.sam@gentoo> (raw)
commit: 27f17b985f46015bd296d11976cac73e11532655
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Feb 6 03:03:34 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Feb 6 03:03:34 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=27f17b98
sys-libs/libnvme: revbump for Python fix
Followup to ba65982faccd363da37bc8953ee51b4475727876. parona made a fair point
that a revbump is technically warranted given that with USE=python, we may
get an additional impl installed outside of what PYTHON_TARGETS covered
(e.g. if configure picks up Python 3.12, builds & installs that, then the
proper Python impl builds do Python 3.11).
Revbump for correctness accordingly. After he said it, I realised it wasn't
just a technicality, but actually pretty plausible as well.
Bug: https://bugs.gentoo.org/923853
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-libs/libnvme/{libnvme-1.7.1.ebuild => libnvme-1.7.1-r1.ebuild} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
diff --git a/sys-libs/libnvme/libnvme-1.7.1.ebuild b/sys-libs/libnvme/libnvme-1.7.1-r1.ebuild
similarity index 100%
rename from sys-libs/libnvme/libnvme-1.7.1.ebuild
rename to sys-libs/libnvme/libnvme-1.7.1-r1.ebuild
next reply other threads:[~2024-02-06 3:05 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 3:05 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-31 20:37 [gentoo-commits] repo/gentoo:master commit in: sys-libs/libnvme/ Patrick McLean
2024-10-31 20:37 Patrick McLean
2024-09-23 8:18 Arthur Zamarin
2024-09-23 7:13 Arthur Zamarin
2024-09-23 0:32 Sam James
2024-08-05 18:50 Patrick McLean
2024-06-25 2:39 Sam James
2024-06-25 2:39 Sam James
2024-05-16 14:58 Arthur Zamarin
2024-05-03 21:57 Patrick McLean
2024-03-24 11:35 Sam James
2024-03-24 11:29 Sam James
2024-02-14 18:30 Patrick McLean
2024-02-06 5:36 Sam James
2024-02-06 2:56 Sam James
2024-02-03 6:56 Sam James
2024-02-02 17:51 Arthur Zamarin
2024-02-02 13:34 Arthur Zamarin
2024-02-02 12:38 Arthur Zamarin
2024-02-02 5:13 Sam James
2023-12-21 0:07 Ionen Wolkens
2023-12-20 11:08 Sam James
2023-12-10 1:38 Ionen Wolkens
2023-12-09 7:54 Arthur Zamarin
2023-11-24 9:31 Sam James
2023-11-08 5:35 Sam James
2023-11-08 5:35 Sam James
2023-11-08 1:50 Sam James
2023-11-08 1:50 Sam James
2023-11-08 1:50 Sam James
2023-11-04 10:52 Sam James
2023-11-02 14:41 Joonas Niilola
2023-10-26 13:04 Sam James
2023-09-29 7:05 Patrick McLean
2023-09-13 5:38 Sam James
2023-08-19 15:37 Arthur Zamarin
2023-08-19 9:24 Sam James
2023-08-19 6:23 Sam James
2023-07-09 4:39 Sam James
2023-07-09 4:37 Sam James
2023-07-09 2:13 Sam James
2023-06-30 23:14 Patrick McLean
2023-05-29 20:18 Sam James
2023-05-27 10:57 Arthur Zamarin
2023-05-23 15:16 Arthur Zamarin
2023-05-23 15:16 Arthur Zamarin
2023-04-07 5:07 Sam James
2023-04-07 5:07 Sam James
2023-04-07 5:07 Sam James
2023-04-07 5:07 Sam James
2023-03-31 19:13 Patrick McLean
2023-01-31 23:06 Patrick McLean
2022-12-26 8:35 Sam James
2022-12-25 22:06 David Seifert
2022-11-25 6:02 Sam James
2022-11-25 5:16 Sam James
2022-11-25 5:16 Sam James
2022-11-25 5:16 Sam James
2022-11-14 22:15 Patrick McLean
2022-11-03 20:59 Patrick McLean
2022-10-31 18:07 Patrick McLean
2022-10-31 17:50 Patrick McLean
2022-08-01 18:56 Zac Medico
2022-07-28 13:59 Sam James
2022-05-19 11:24 WANG Xuerui
2022-04-09 19:48 Zac Medico
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=1707188614.27f17b985f46015bd296d11976cac73e11532655.sam@gentoo \
--to=sam@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