From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>, 61881@debbugs.gnu.org
Subject: bug#61881: Failed install with 1.4.0 installer-dump-2464c73a
Date: Thu, 02 Mar 2023 10:02:50 +0100 [thread overview]
Message-ID: <87edq7le4l.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87r0u8vws7.fsf@contorta>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
Hi Vagrant,
Vagrant Cascadian <vagrant@debian.org> writes:
>> Can you look into directories like /tmp/dump.XXXXX? There should be
>> a .tar.gz somewhere of the dump.
>
> No, that was probably lost when I powered it down. If the dump was
> stored on the to-be-installed-filesystem somewhere, there might be a
> chance to recover it?
No, unfortunately, it's only on the /tmp of the live system.
> I had assumed when it said it uploaded the installer dump that it had
> done so successfully... (maybe a way to more easily confirm success or
> failure of the dump upload might be worth implementing?)
You mean, manually checking that the upload is actually present on the
server? That could be doable, right.
> Ah well, I will try again with that installer and/or the "latest"
> installer ... and if I still have similar issues will report back
> ... and will be more determined to capture any relevent dump files!
>
> If I feel adventurous, I might even try on the new laptop itself. :)
Have fun 😇
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-03-02 9:04 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 [this message]
2023-03-06 22:59 ` Ludovic Courtès
2023-03-13 23:21 ` bug#61881: Failed install with 1.4.0 installer-dump-2464c83a Vagrant Cascadian
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=87edq7le4l.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=61881@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=vagrant@debian.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 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).