From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/starpu/
Date: Wed, 14 Jul 2021 18:11:08 +0000 (UTC) [thread overview]
Message-ID: <1626286259.634532dffd1fe2cb987e4147cedba2f533396cd1.marecki@gentoo> (raw)
commit: 634532dffd1fe2cb987e4147cedba2f533396cd1
Author: Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Wed Jul 14 18:02:25 2021 +0000
Commit: Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Wed Jul 14 18:10:59 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=634532df
dev-libs/starpu-1.2.6-r1: change the subslot
As mentioned in the previous commit, the major SOVERSION of the library
this ebuild installs is 5 and I haven't seen any indication of where the
8 might have come from, neither in the source code nor in g.g.o repo
history (it just shows up in place of 0 one day). Probably doesn't
matter though, this package has only got one revdep in the tree and that
one doesn't depend on any specific subslots.
Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>
dev-libs/starpu/starpu-1.2.6-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/starpu/starpu-1.2.6-r1.ebuild b/dev-libs/starpu/starpu-1.2.6-r1.ebuild
index a75f91f978a..858987550d0 100644
--- a/dev-libs/starpu/starpu-1.2.6-r1.ebuild
+++ b/dev-libs/starpu/starpu-1.2.6-r1.ebuild
@@ -11,7 +11,7 @@ HOMEPAGE="http://starpu.gforge.inria.fr/"
SRC_URI="https://gforge.inria.fr/frs/download.php/file/37744/${P}.tar.gz"
LICENSE="LGPL-2.1"
-SLOT="0/8"
+SLOT="0/5"
KEYWORDS="~alpha amd64 ~arm ~ia64 ~ppc ~ppc64 ~riscv ~sparc x86 ~amd64-linux ~x86-linux"
IUSE="
next reply other threads:[~2021-07-14 18:11 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 18:11 Marek Szuba [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-09 22:56 [gentoo-commits] repo/gentoo:master commit in: dev-libs/starpu/ Andreas K. Hüttel
2024-11-09 22:42 Andreas K. Hüttel
2023-05-14 17:11 Sam James
2023-02-19 18:25 Sam James
2022-12-05 5:30 WANG Xuerui
2022-05-16 8:12 David Seifert
2022-01-10 23:02 Sam James
2021-12-27 14:13 Agostino Sarubbo
2021-12-26 20:51 Arthur Zamarin
2021-12-26 19:51 Arthur Zamarin
2021-12-26 19:05 Sam James
2021-12-26 19:05 Sam James
2021-12-26 19:03 Sam James
2021-11-19 17:36 Arthur Zamarin
2021-11-14 23:51 Sam James
2021-10-29 4:30 Sam James
2021-10-29 4:27 Sam James
2021-10-29 2:36 Sam James
2021-10-24 21:14 Sam James
2021-10-02 23:17 Sam James
2021-07-16 11:43 Marek Szuba
2021-07-14 22:45 Marek Szuba
2021-07-14 16:15 Marek Szuba
2020-11-14 1:48 Thomas Deutschmann
2020-09-19 12:51 Michał Górny
2019-12-12 14:58 Michał Górny
2019-02-16 9:28 Pacho Ramos
2019-02-11 14:40 Mikle Kolyada
2018-09-23 12:44 Jeroen Roovers
2018-09-23 11:46 Jeroen Roovers
2018-09-23 11:46 Jeroen Roovers
2018-01-24 22:52 Andreas Sturmlechner
2017-11-27 19:46 Sergei Trofimovich
2017-09-30 2:58 Sergei Trofimovich
2017-09-02 13:18 Michael Palimaka
2017-07-01 9:52 Sergei Trofimovich
2017-04-29 16:21 Jeroen Roovers
2017-04-05 15:36 Michael Weber
2016-06-09 1:15 Sebastien Fabbro
2016-06-07 16:47 Tobias Klausmann
2016-02-17 19:39 Sebastien Fabbro
2016-02-17 17:18 Sebastien Fabbro
2016-02-17 17:18 Sebastien Fabbro
2016-02-17 17:18 Sebastien Fabbro
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=1626286259.634532dffd1fe2cb987e4147cedba2f533396cd1.marecki@gentoo \
--to=marecki@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