From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-gfx/cura/
Date: Wed, 7 Oct 2020 00:59:51 +0000 (UTC) [thread overview]
Message-ID: <1602030861.b5ab283eeb1138e743831f3f04d29c04e58d9ecc.sam@gentoo> (raw)
commit: b5ab283eeb1138e743831f3f04d29c04e58d9ecc
Author: D G Turner <digitall <AT> scummvm <DOT> org>
AuthorDate: Sat Sep 26 13:14:21 2020 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Oct 7 00:34:21 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b5ab283e
media-gfx/cura: Fix runtime crash at startup (4.6.1)
This needs to resolve the correct dependencies i.e. v4.6.1, not later
such as v4.7.0 as this will likely cause issues.
Signed-off-by: David G Turner <digitall <AT> scummvm.org>
Signed-off-by: Sam James <sam <AT> gentoo.org>
media-gfx/cura/{cura-4.6.1.ebuild => cura-4.6.1-r1.ebuild} | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/media-gfx/cura/cura-4.6.1.ebuild b/media-gfx/cura/cura-4.6.1-r1.ebuild
similarity index 83%
rename from media-gfx/cura/cura-4.6.1.ebuild
rename to media-gfx/cura/cura-4.6.1-r1.ebuild
index bbd5d0b29de..943f9305325 100644
--- a/media-gfx/cura/cura-4.6.1.ebuild
+++ b/media-gfx/cura/cura-4.6.1-r1.ebuild
@@ -20,11 +20,11 @@ REQUIRED_USE="${PYTHON_REQUIRED_USE}"
BDEPEND="sys-devel/gettext"
RDEPEND="${PYTHON_DEPS}
- >=dev-libs/libcharon-${PV:0:3}[${PYTHON_SINGLE_USEDEP}]
- >=dev-libs/libsavitar-${PV:0:3}:=[python,${PYTHON_SINGLE_USEDEP}]
- >=dev-python/uranium-${PV:0:3}[${PYTHON_SINGLE_USEDEP}]
- >=media-gfx/curaengine-${PV:0:3}
- >=media-gfx/fdm-materials-${PV:0:3}
+ ~dev-libs/libcharon-${PV}[${PYTHON_SINGLE_USEDEP}]
+ ~dev-libs/libsavitar-${PV}:=[python,${PYTHON_SINGLE_USEDEP}]
+ ~dev-python/uranium-${PV}[${PYTHON_SINGLE_USEDEP}]
+ ~media-gfx/curaengine-${PV}
+ ~media-gfx/fdm-materials-${PV}
$(python_gen_cond_dep '
dev-python/requests[${PYTHON_MULTI_USEDEP}]
dev-python/sentry-sdk[${PYTHON_MULTI_USEDEP}]
next reply other threads:[~2020-10-07 0:59 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 0:59 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-09 10:52 [gentoo-commits] repo/gentoo:master commit in: media-gfx/cura/ Matthew Smith
2022-05-09 7:00 Michał Górny
2022-05-08 19:59 Sam James
2022-05-08 8:47 Michał Górny
2022-03-10 21:21 Jakov Smolić
2022-03-05 11:54 Matthew Smith
2022-03-05 11:54 Matthew Smith
2022-02-28 19:43 Matthew Smith
2022-02-28 19:43 Matthew Smith
2022-02-13 22:38 Jakov Smolić
2022-02-11 20:25 Arthur Zamarin
2021-11-10 19:44 Jonas Stein
2021-06-10 17:41 Dennis Lamm
2021-02-07 23:57 Dennis Lamm
2021-02-07 23:57 Dennis Lamm
2020-12-14 0:46 Sam James
2020-11-30 18:37 Dennis Lamm
2020-11-30 18:37 Dennis Lamm
2020-11-30 18:37 Dennis Lamm
2020-10-11 11:25 Dennis Lamm
2020-10-07 0:59 Sam James
2020-10-07 0:59 Sam James
2020-10-07 0:59 Sam James
2020-09-19 16:34 Sam James
2020-05-25 21:04 Alexey Shvetsov
2020-02-09 16:29 Michał Górny
2019-10-16 5:22 Joonas Niilola
2019-01-02 22:05 Amy Liffey
2019-01-02 21:52 Amy Liffey
2018-07-16 17:29 Amy Liffey
2018-06-14 20:14 Alexey Shvetsov
2018-04-15 14:06 Amy Liffey
2018-04-03 15:28 Jonas Stein
2017-11-26 23:02 David Seifert
2017-07-23 11:05 Alexey Shvetsov
2017-04-23 20:48 Michał Górny
2016-08-08 1:49 Göktürk Yüksek
2016-08-08 1:49 Göktürk Yüksek
2016-05-22 17:05 Göktürk Yüksek
2016-04-29 11:35 Alexey Shvetsov
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=1602030861.b5ab283eeb1138e743831f3f04d29c04e58d9ecc.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