unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Csepp <raingloom@riseup.net>
Cc: kiasoc5 <kiasoc5@disroot.org>, help-guix@gnu.org
Subject: Re: How to avoid downloading qtbase:debug
Date: Sat, 22 Oct 2022 17:28:03 +0200	[thread overview]
Message-ID: <87lep7n9th.fsf@nckx> (raw)
In-Reply-To: <87r0z0cfa3.fsf@riseup.net>

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

Hi!

kiasoc5 写道:
> =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?

If this is what I suspect it is, the only way would be ‘guix shell 
--no-grafts’.  This will disable any security fixes that haven't 
yet made it to master.

I don't recommend it, beyond testing it to see if grafts are 
indeed to blame, and perhaps narrowing down how.

> Is this a bug?

If it is due to grafting, it's a long-time known annoyance, yes. 
I searched (twice) to find a specific open bug report to give you, 
but found nothing.

(Almost certainly a failure on my part; don't open a new one ;-)

I say annoyance because it's nothing more for most people, but if 
bandwidth is a serious issue for you the best way to see it fixed 
is to dig in.

Csepp 写道:
> guix shell always downloads every output of all the packages.

All generalisations are false, as they say:

~ λ guix shell qtbase
…
19.4 MB will be downloaded
 qtbase-6.3.1  18.5MiB …
𝕘 qtbase ~ λ exit

~ λ guix shell qtbase:debug
…
321.6 MB will be downloaded
 qtbase-6.3.1-debug  288.2MiB …
𝕘 qtbase:debug ~ λ exit

Kind regards,

T G-R

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

  parent reply	other threads:[~2022-10-24  7:16 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 [this message]
2022-10-22 19:27   ` Efraim Flashner
2022-10-27 17:03     ` Maxim Cournoyer
2022-11-18 16:37 ` Ludovic Courtès

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=87lep7n9th.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=kiasoc5@disroot.org \
    --cc=raingloom@riseup.net \
    /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).