all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julius Schwartzenberg <julius.schwartzenberg@gmail.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 60207@debbugs.gnu.org
Subject: bug#60207: Bug report
Date: Tue, 20 Dec 2022 20:51:45 +0100	[thread overview]
Message-ID: <033742a9-7892-b837-2d04-422704b84385@gmail.com> (raw)
In-Reply-To: <87wn6mifjy.fsf@pelzflorian.de>

Hi Florian,

Op 20-12-2022 om 10:34 schreef pelzflorian (Florian Pelz):
> does it work if you do this before pull?
> 
> sudo guix archive --authorize < $(dirname $(which guix))/../share/guix/bordeaux.guix.gnu.org.pub

When I do this, I get:
> julius@tinkerboard:~$ sudo guix archive --authorize < $(dirname $(which guix))/../share/guix/bordeaux.guix.gnu.org.pub
> bash: /usr/local/bin/../share/guix/bordeaux.guix.gnu.org.pub: No such file or directory

Might there be something wrong with the installation?


> Then it would compile fine on the bordeaux build farm and you could
> download the substitute from there.

Yes, I am not sure why it seems to try to compile so much. I assumed ARM 
builds might not be available. I'd rather avoid compiling anything 
locally as this ARM board has little resources for this.

Thanks!!
Julius




  reply	other threads:[~2022-12-20 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 17:48 bug#60207: Bug report Julius Schwartzenberg
2022-12-20  9:34 ` pelzflorian (Florian Pelz)
2022-12-20 19:51   ` Julius Schwartzenberg [this message]
2022-12-21 15:26     ` pelzflorian (Florian Pelz)
2022-12-23 20:00       ` Julius Schwartzenberg
2022-12-24 21:40         ` pelzflorian (Florian Pelz)
2022-12-25 15:35           ` Julius Schwartzenberg
2022-12-26 12:09             ` bug#60207: ci build of latest guix for armhf pelzflorian (Florian Pelz)
2022-12-28 18:14               ` Christopher Baines

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=033742a9-7892-b837-2d04-422704b84385@gmail.com \
    --to=julius.schwartzenberg@gmail.com \
    --cc=60207@debbugs.gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /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.