public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/mdds/
Date: Tue,  8 Feb 2022 23:53:04 +0000 (UTC)	[thread overview]
Message-ID: <1644364364.6e1eb456ac6c89ee5bf1f0045bc043a2cf3e829a.dilfridge@gentoo> (raw)

commit:     6e1eb456ac6c89ee5bf1f0045bc043a2cf3e829a
Author:     Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Tue Feb  8 23:52:44 2022 +0000
Commit:     Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Tue Feb  8 23:52:44 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6e1eb456

dev-util/mdds: Fix subslot in live ebuild

Closes: https://bugs.gentoo.org/830465
Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org>

 dev-util/mdds/mdds-9999.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-util/mdds/mdds-9999.ebuild b/dev-util/mdds/mdds-9999.ebuild
index dc57a4506ee2..6abe223c7965 100644
--- a/dev-util/mdds/mdds-9999.ebuild
+++ b/dev-util/mdds/mdds-9999.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2021 Gentoo Authors
+# Copyright 1999-2022 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
@@ -16,7 +16,7 @@ DESCRIPTION="Collection of multi-dimensional data structure and indexing algorit
 HOMEPAGE="https://gitlab.com/mdds/mdds"
 
 LICENSE="MIT"
-SLOT="1/${PV%.*}" # Check API version on version bumps!
+SLOT="1/2.0" # Check API version on version bumps!
 IUSE="doc openmp valgrind test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2022-02-08 23:53 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 23:53 Andreas K. Hüttel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-20 20:49 [gentoo-commits] repo/gentoo:master commit in: dev-util/mdds/ Andreas Sturmlechner
2024-02-20  5:56 Sam James
2024-02-17  9:55 Arthur Zamarin
2024-02-12 10:31 Sam James
2024-01-27  0:48 Andreas Sturmlechner
2024-01-27  0:48 Andreas Sturmlechner
2023-08-30 23:52 Sam James
2023-05-14 17:11 Sam James
2023-02-25 10:27 Andreas Sturmlechner
2022-08-12 12:26 WANG Xuerui
2022-08-12 12:26 WANG Xuerui
2022-06-14  7:21 Agostino Sarubbo
2022-05-18 11:13 Andreas Sturmlechner
2022-05-15 10:55 Andreas Sturmlechner
2022-05-14 21:30 David Seifert
2022-04-27 21:57 Sam James
2022-04-10 10:46 Sam James
2022-03-12 15:53 Andreas Sturmlechner
2021-12-29 13:46 Yixun Lan
2021-11-14  5:25 Sam James
2020-11-23  9:47 Sam James
2020-11-23  4:52 Sam James
2020-11-23  3:58 Sam James
2020-05-31 15:40 Mikle Kolyada
2020-05-28 17:09 Andreas Sturmlechner
2020-05-20 13:35 Mikle Kolyada
2020-05-19 19:36 Mikle Kolyada
2020-04-10 13:48 Andreas Sturmlechner
2020-03-16 21:29 Andreas Sturmlechner
2019-07-31 21:11 Aaron Bauman
2019-06-18 18:24 Thomas Deutschmann
2019-06-09 20:16 Mikle Kolyada
2019-03-12  7:10 Andreas Sturmlechner
2018-11-15 23:12 Andreas Sturmlechner
2018-09-16 22:34 Andreas Sturmlechner
2018-09-16 22:34 Andreas Sturmlechner
2018-09-12 20:56 Andreas Sturmlechner
2017-12-29 23:06 Andreas Sturmlechner
2017-12-29 18:03 Mikle Kolyada
2017-12-28 19:35 Andreas Sturmlechner
2017-12-26  0:59 Thomas Deutschmann
2017-11-19 23:49 Andreas Sturmlechner
2017-11-14 14:13 Manuel Rüger
2017-11-11 21:17 Andreas Sturmlechner
2017-11-11 21:17 Andreas Sturmlechner
2017-11-10 19:20 Andreas Sturmlechner
2017-11-10 19:20 Andreas Sturmlechner
2017-11-08  8:55 Andreas Sturmlechner
2016-12-17 15:57 Andreas Hüttel
2016-12-03 23:00 Andreas Hüttel
2016-11-29 18:41 Agostino Sarubbo
2016-11-29 18:40 Agostino Sarubbo
2016-09-17 21:32 Andreas Hüttel
2016-09-17 21:32 Andreas Hüttel
2016-06-03 12:50 Lars Wendler
2016-06-03 12:50 Lars Wendler
2016-06-03 12:50 Lars Wendler
2016-02-22 17:07 Andreas Hüttel

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=1644364364.6e1eb456ac6c89ee5bf1f0045bc043a2cf3e829a.dilfridge@gentoo \
    --to=dilfridge@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