unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: kiasoc5 <kiasoc5@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: How to avoid downloading qtbase:debug
Date: Fri, 18 Nov 2022 17:37:12 +0100	[thread overview]
Message-ID: <87pmdk9q2v.fsf@gnu.org> (raw)
In-Reply-To: <20221022013952.49dfa544@aria> (kiasoc5@disroot.org's message of "Sat, 22 Oct 2022 01:39:52 +0000")

Hi!

kiasoc5 <kiasoc5@disroot.org> skribis:

> =guix shell qtbase= downloads the entire debug output of qtbase even
> though I didn't write down qtbase:debug. That's hundreds of megabytes
> of bandwith I didn't want to use. How do I avoid downloading the debug
> output? Is this a bug?

Yes, it’s an unfortunate bug:

  https://issues.guix.gnu.org/30952

Would be good to look into it again with a fresh mind!

Ludo’.


      parent reply	other threads:[~2022-11-18 16:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22  1:39 How to avoid downloading qtbase:debug kiasoc5
2022-10-22 10:39 ` Csepp
2022-10-22 14:28   ` Maxim Cournoyer
2022-10-22 15:37     ` Csepp
2022-10-22 15:28   ` Tobias Geerinckx-Rice
2022-10-22 19:27   ` Efraim Flashner
2022-10-27 17:03     ` Maxim Cournoyer
2022-11-18 16:37 ` Ludovic Courtès [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=87pmdk9q2v.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=kiasoc5@disroot.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).