unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [core-updates-frozen] Attempt julia@1.6.4 (upgrade)
Date: Mon, 13 Dec 2021 22:20:27 -0500	[thread overview]
Message-ID: <87r1afc1ok.fsf@gmail.com> (raw)
In-Reply-To: <858rxa1t0b.fsf@gmail.com> (zimoun's message of "Fri, 26 Nov 2021 22:55:48 +0100")

Hi Simon,

zimoun <zimon.toutoune@gmail.com> writes:

> Hi,
>
> First, I am not convinced that upgrade Julia from 1.6.3 to 1.6.4 is
> something to do now; especially when the branch is “frozen”.  Using
> patches #52117 [1], all failures are fixed for 1.6.3.
>
> 1: https://issues.guix.gnu.org/52117
>
>
> Here a rough attempt which replaces the source of 1.6.3 by 1.6.4 and
> many tests are deeply broken (broken precompile is not a good sign, at
> all ;-)).  Well, it seems expected regarding the complexity of the Julia
> stack. :-)
>
> Therefore, the upgrade requires various other upgrades elsewhere and
> probably some fixes with couple of patches.  As it had been for previous
> Julia upgrades. :-)
>
> Then, using this upgraded julia@1.6.4, there is a high probability that
> many julia-* packages would be broken too and thus they would require
> fixes.
>
> IMHO, if we want a working Julia in the delay for the merge, the best
> seems to just apply patch#52117 and let this Julia upgrade for another
> round.  For what my opinion is here. :-)

Seems I had not answered here; thanks for attempting my suggestion!  It
seems you were right that Julia (even for a patch version bump) is
picky.

It'll have to be resolved on core-updates :-).

Thanks,

Maxim


  reply	other threads:[~2021-12-14  3:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26 21:55 [core-updates-frozen] Attempt julia@1.6.4 (upgrade) zimoun
2021-12-14  3:20 ` Maxim Cournoyer [this message]
2021-12-14  6:28   ` zimoun
2021-12-14 19:40     ` Maxim Cournoyer

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r1afc1ok.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).