From: Akib Azmain Turja <akib@disroot.org>
To: help-guix@gnu.org
Subject: First guix pull is too costly
Date: Tue, 28 Jun 2022 15:05:27 +0600 [thread overview]
Message-ID: <87sfnpkvjc.fsf@disroot.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
Hello,
Yesterday, I created a new user in my system. Then I tried to install a
package, but found that it's not the latest, although I did sudo guix
pull before sudo guix system reconfigure. So I tried to do guix pull,
but it seems to clone the whole repository from scratch. But,
unfortunately, it never succeeds due to my faulty network connection.
It progresses somewhat like 5%, 7%, 20%, and my connection fails, and I
have to start again from the beginning.
Is possible to reuse the guix channel from any other user to do the
first guix pull? Or maybe a shallow clone?
--
Akib Azmain Turja
This message is signed by me with my GnuPG key. It's fingerprint is:
7001 8CE5 819F 17A3 BBA6 66AF E74F 0EFA 922A E7F5
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2022-06-28 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 9:05 Akib Azmain Turja [this message]
2022-08-17 10:00 ` First guix pull is too costly zimoun
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=87sfnpkvjc.fsf@disroot.org \
--to=akib@disroot.org \
--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).