all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Josselin Poiret <dev@jpoiret.xyz>, 61881@debbugs.gnu.org
Subject: bug#61881: Failed install with 1.4.0 installer-dump-2464c83a
Date: Mon, 13 Mar 2023 16:21:39 -0700	[thread overview]
Message-ID: <875yb4nsos.fsf@wireframe> (raw)
In-Reply-To: <878rg9fpvk.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 853 bytes --]

On 2023-03-06, Ludovic Courtès wrote:
> Vagrant Cascadian <vagrant@debian.org> skribis:
>
>> On 2023-03-01, Josselin Poiret wrote:
>>> Vagrant Cascadian <vagrant@debian.org> writes:
>
> [...]
>
>>> I can't find the installer dump on dump.guix.gnu.org unfortunately
>>> :(.
>>
>> It is possible I typoed it somehow, as I filed the report on another
>> machine and eyeballed the name...
>
> I used my superpowers and found the typo:
>
>   https://dump.guix.gnu.org/download/installer-dump-2464c83a

Thanks for tracking that down!

At any rate, I successfully managed to install on both on physical and
virtual hardware...

My guess with what caused the original failure was an unstable wireless
connection on the host system.

My latter installs on the hardware itself, and a virtual machine as
well.

live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

      reply	other threads:[~2023-03-13 23:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  0:36 bug#61881: Failed install with 1.4.0 installer-dump-2464c73a Vagrant Cascadian
2023-03-01 10:14 ` Josselin Poiret via Bug reports for GNU Guix
2023-03-02  0:09   ` Vagrant Cascadian
2023-03-02  9:02     ` Josselin Poiret via Bug reports for GNU Guix
2023-03-06 22:59     ` Ludovic Courtès
2023-03-13 23:21       ` Vagrant Cascadian [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=875yb4nsos.fsf@wireframe \
    --to=vagrant@debian.org \
    --cc=61881@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=ludo@gnu.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.
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.