From: Greg Hogan <code@greghogan.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: help-guix@gnu.org, Andreas Enge <andreas@enge.fr>
Subject: Re: URISyntaxException building openjdk@10
Date: Tue, 31 Oct 2023 13:40:46 -0400 [thread overview]
Message-ID: <CA+3U0Z=UUE5_rPV9vdZHARMrC7KTvhCXUaLttMFkY+Lug740Qg@mail.gmail.com> (raw)
In-Reply-To: <85937F68-27F8-41F9-82E2-1434DE0CC5B2@lepiller.eu>
On Mon, Jul 24, 2023 at 4:53 AM Julien Lepiller <julien@lepiller.eu> wrote:
>
> Which architecture are you building on, and which filesystem is your store on? This looks like something got corrupted, maybe check your filesystem or try and rebuild openjdk@9 (with --check --no-grafts). As Andreas mentions, it works on the build farm.
>
> Le 24 juillet 2023 10:17:54 GMT+02:00, Andreas Enge <andreas@enge.fr> a écrit :
> >Hello Greg,
> >
> >Am Thu, Jul 20, 2023 at 11:32:40AM -0400 schrieb Greg Hogan:
> >> I have tried everything I could think of but have been unable to build
> >> openjdk@10 since the final core-updates merge. Am simply running `guix
> >> build openjdk` from a recent `guix pull`.
> >
> >openjdk and openjdk@10 are both available as substitutes. Maybe authorising
> >the substitute servers will solve your problem?
> >
> >Also I have been rebuilding openjdk a few times before the core-updates
> >merge since they required patches, and definitely it worked in the end.
> >
> >Andreas
I am on AWS and recently switched from an r6i (Intel) instance to r7a
(AMD) and openjdk now builds successfully. ¯\_(ツ)_/¯
I would rule out filesystem corruption as /gnu/store and /var/guix are
on an attached volume which I moved to and continued to use on the new
instance.
Greg
prev parent reply other threads:[~2023-10-31 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 15:32 URISyntaxException building openjdk@10 Greg Hogan
2023-07-24 8:17 ` Andreas Enge
2023-07-24 8:52 ` Julien Lepiller
2023-10-31 17:40 ` Greg Hogan [this message]
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='CA+3U0Z=UUE5_rPV9vdZHARMrC7KTvhCXUaLttMFkY+Lug740Qg@mail.gmail.com' \
--to=code@greghogan.com \
--cc=andreas@enge.fr \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
/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.