From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-mathematics/maxima/
Date: Wed, 14 Sep 2022 12:52:28 +0000 (UTC) [thread overview]
Message-ID: <1663159681.da876bb7967ac450e1986fca23382881dd441229.mjo@gentoo> (raw)
commit: da876bb7967ac450e1986fca23382881dd441229
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Wed Sep 14 12:48:01 2022 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Wed Sep 14 12:48:01 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=da876bb7
sci-mathematics/maxima: disable the failing test suite.
Stabilization of maxima-5.46.0 is pending, but its test suite fails even
after disabling a chunk of unmaintained "share" tests. The failures have
all been reported upstream; for now let's just turn it off so we don't
annoy users.
Bug: https://bugs.gentoo.org/867547
Closes: https://bugs.gentoo.org/838202
Signed-off-by: Michael Orlitzky <mjo <AT> gentoo.org>
sci-mathematics/maxima/maxima-5.46.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sci-mathematics/maxima/maxima-5.46.0.ebuild b/sci-mathematics/maxima/maxima-5.46.0.ebuild
index e6051e772c32..8101640819ba 100644
--- a/sci-mathematics/maxima/maxima-5.46.0.ebuild
+++ b/sci-mathematics/maxima/maxima-5.46.0.ebuild
@@ -16,7 +16,7 @@ SLOT="0"
KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-linux"
IUSE="clisp clozurecl clozurecl64 cmucl ecls emacs gcl gui nls +sbcl vtk X test"
-RESTRICT="!test? ( test )"
+RESTRICT="test" # bug 838202
# Languages
LANGS="de es pt pt_BR"
next reply other threads:[~2022-09-14 12:52 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 12:52 Michael Orlitzky [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-01 20:56 [gentoo-commits] repo/gentoo:master commit in: sci-mathematics/maxima/ Michael Orlitzky
2024-06-04 6:33 Andrey Grozin
2023-11-22 23:18 Michael Orlitzky
2023-07-22 15:19 Andrey Grozin
2023-06-01 15:38 Andrey Grozin
2023-06-01 15:37 Andrey Grozin
2023-05-25 8:32 Andrey Grozin
2023-04-23 5:36 Jakov Smolić
2023-04-19 11:52 Sam James
2023-02-16 13:18 Andrey Grozin
2023-01-22 6:29 Andrey Grozin
2022-09-19 19:49 Andreas Sturmlechner
2022-09-16 8:31 Ulrich Müller
2022-09-15 6:47 Agostino Sarubbo
2022-04-14 11:46 Andrey Grozin
2022-04-13 8:48 Andrey Grozin
2022-04-13 8:48 Andrey Grozin
2021-11-18 23:50 Georgy Yakovlev
2021-07-17 18:58 Michael Orlitzky
2021-06-22 22:38 Sam James
2021-06-21 4:09 Andrey Grozin
2021-06-21 4:07 Andrey Grozin
2021-06-09 10:29 Andrey Grozin
2021-04-02 1:03 Michael Orlitzky
2021-03-30 12:43 Michael Orlitzky
2021-03-29 13:47 Michael Orlitzky
2021-03-29 13:47 Michael Orlitzky
2021-03-26 0:57 Michael Orlitzky
2020-11-05 20:25 Andreas Sturmlechner
2020-07-23 7:03 Kent Fredric
2020-06-08 14:10 Andrey Grozin
2020-04-07 15:08 Andrey Grozin
2020-03-27 3:49 Michael Orlitzky
2020-03-27 3:44 Michael Orlitzky
2020-01-30 15:44 Andrey Grozin
2020-01-30 15:42 Andrey Grozin
2019-12-20 22:49 Ulrich Müller
2019-12-20 10:11 Ulrich Müller
2019-04-28 22:06 Thomas Deutschmann
2019-04-08 14:13 Mikle Kolyada
2019-03-15 15:38 Andrey Grozin
2019-03-12 18:32 Andrey Grozin
2018-10-18 16:51 Andrey Grozin
2018-09-05 15:22 Andrey Grozin
2018-01-07 16:57 Ulrich Müller
2017-12-31 13:32 Andrey Grozin
2017-12-31 5:00 Andrey Grozin
2017-10-05 15:59 Andrey Grozin
2017-05-30 19:38 Andrey Grozin
2016-12-29 10:05 Agostino Sarubbo
2016-12-11 12:04 Andrey Grozin
2016-06-06 11:53 Andrey Grozin
2016-05-14 7:54 Andrey Grozin
2016-05-14 7:53 Andrey Grozin
2016-03-18 11:18 Andrey Grozin
2016-03-05 16:26 Mikle Kolyada
2015-12-25 11:47 Andrey Grozin
2015-12-23 11:29 Ulrich Müller
2015-12-23 8:20 Ulrich Müller
2015-11-27 12:08 Andrey Grozin
2015-11-10 5:09 Andrey Grozin
2015-11-10 5:07 Andrey Grozin
2015-09-18 4:25 Andrey Grozin
2015-09-18 4:23 Andrey Grozin
2015-09-03 18:57 Andrey Grozin
2015-08-26 12:31 Guilherme Amadio
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=1663159681.da876bb7967ac450e1986fca23382881dd441229.mjo@gentoo \
--to=mjo@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