From: "(" <paren@disroot.org>
To: "mhrunnels@yahoo.com" <mhrunnels@yahoo.com>,
"help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Guix Pull - Device or Resource Busy
Date: Sun, 08 Jan 2023 22:09:21 +0000 [thread overview]
Message-ID: <CPN5HH3Z2O2A.1RUL1Z3KO8FED@guix-framework> (raw)
In-Reply-To: <1827448990.5046781.1673202056151@mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 349 bytes --]
On Sun Jan 8, 2023 at 6:20 PM GMT, mhrunnels@yahoo.com via wrote:
> However, I have been unable to capture the standard screen output for analysis. All attempts to direct the output using pipes "|" or redirection ">" have failed.
Have you tried redirecting stderr with ``2>''?
guix pull --verbosity=3 --debug=5 2>guix-pull.log
-- (
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-01-08 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1827448990.5046781.1673202056151.ref@mail.yahoo.com>
2023-01-08 18:20 ` Guix Pull - Device or Resource Busy mhrunnels@yahoo.com via
2023-01-08 22:09 ` ( [this message]
2023-01-08 22:18 ` Timo Wilken
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=CPN5HH3Z2O2A.1RUL1Z3KO8FED@guix-framework \
--to=paren@disroot.org \
--cc=help-guix@gnu.org \
--cc=mhrunnels@yahoo.com \
/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).