From: Tobias Geerinckx-Rice <me@tobias.gr>
To: help-guix@gnu.org
Subject: Re: Fw: `guix pack --format=squashfs rseqc` fails and I'm not sure how to debug this
Date: Wed, 04 Mar 2020 20:22:07 +0100 [thread overview]
Message-ID: <87a74wvscd.fsf@nckx> (raw)
In-Reply-To: <BL0PR06MB46730BA2EF6BE0B5961965C8E9E50@BL0PR06MB4673.namprd06.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 340 bytes --]
Josh Marshall 写道：
> I tried a quick test with `guix pack --format=squashfs rseqc`
> and it fails. I'm not sure how to debug this. Log attached.
This is on CentOS 7, by the way, so my guess on IRC was that the
kernel is too old to ‘read existing filesystem - will not
overwrite - ABORTING!’.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2020-03-04 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BL0PR06MB4673D414B7318D62667990D4E9E50@BL0PR06MB4673.namprd06.prod.outlook.com>
2020-03-04 18:48 ` Fw: `guix pack --format=squashfs rseqc` fails and I'm not sure how to debug this Josh Marshall
2020-03-04 19:22 ` Tobias Geerinckx-Rice [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
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=87a74wvscd.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@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.
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).