From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 73197@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>,
Philippe Virouleau <philippe.virouleau@inria.fr>
Subject: [bug#73197] [PATCH] gnu: julia: Update to 1.9.3.
Date: Wed, 08 Jan 2025 11:44:08 +0100 [thread overview]
Message-ID: <87cygxvb47.fsf@gnu.org> (raw)
In-Reply-To: <87frlw3q3o.fsf@gmail.com> (Simon Tournier's message of "Mon, 06 Jan 2025 16:43:23 +0100")
Hello,
Simon Tournier <zimon.toutoune@gmail.com> skribis:
> I am resuming this patch. And I would like to have it merge before the
> end of this month. In other words, I would like to mention this update
> in the Guix HPC annual report.
Excellent. :-)
> Could we have a julia-team branch and that branch built by CI? It would
> help by saving some resources.
This branch is built already:
<https://ci.guix.gnu.org/jobset/julia-upgrade>.
> From my numbers, ~230 Julia packages fail. Over ~300 packages.
[...]
>> The problem is that the julia-build-system needs to be adapted to the
>> newer versions of Julia.
To be clear, the build failures here have to do with JULIA_LOAD_PATH or
JULIA_DEPOT_PATH somehow not being set to the right value. (That’s why
roughly packages with no dependency other than Julia build fine, while
those that depend on other julia-* packages fails to build.)
I’ve rebased the branch and added debugging helpers I was using.
Protip: when fiddling with the ‘julia’ package, use
‘--without-tests=julia’. :-)
HTH!
Ludo’.
next prev parent reply other threads:[~2025-01-08 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 13:22 [bug#73197] [PATCH] gnu: julia: Update to 1.9.3 Ludovic Courtès
2024-09-16 7:50 ` Efraim Flashner
2024-09-16 9:47 ` Ludovic Courtès
2024-09-20 15:29 ` Simon Tournier
2024-09-22 7:24 ` Efraim Flashner
2025-01-06 15:43 ` Simon Tournier
2025-01-08 10:44 ` Ludovic Courtès [this message]
2025-01-13 18:31 ` Simon Tournier
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=87cygxvb47.fsf@gnu.org \
--to=ludovic.courtes@inria.fr \
--cc=73197@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=philippe.virouleau@inria.fr \
--cc=zimon.toutoune@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.