unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
* 79-GiB opam checkout in ~/.cache/guix
@ 2019-11-18 22:58 Tobias Geerinckx-Rice
  2019-11-19  0:03 ` Bengt Richter
  0 siblings, 1 reply; 2+ messages in thread
From: Tobias Geerinckx-Rice @ 2019-11-18 22:58 UTC (permalink / raw)
  To: Guix Devel

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

Auntie Guix,

My SSD hurts & my ~/.cache/guix feels funny:

  ~ λ du -hs ~/.cache/guix/checkouts/* | sort -h
  560K	/home/nckx/.cache/guix/checkouts/hp4…
  1.3M	/home/nckx/.cache/guix/checkouts/l74…
  2.5M	/home/nckx/.cache/guix/checkouts/hep…
  219M	/home/nckx/.cache/guix/checkouts/pjm…
  79G	/home/nckx/.cache/guix/checkouts/f5u…

…wait, what the hell is that last one?

  ~ λ cat ~/.cache/guix/checkouts/f5u…/.git/config
  [core]
	bare = false
	repositoryformatversion = 0
	filemode = true
	logallrefupdates = true
  [remote "origin"]
	url = https://github.com/ocaml/opam-repository
	fetch = +refs/heads/*:refs/remotes/origin/*

I have no idea what this means or what has happened.  I don't 
remember running an opam importer recently, although I've probably 
run ‘guix refresh’ on an opam package or so.

Still.

According to GitHub, the repository is only 70.9 *MiB* and when I 
clone it locally it's still nowhere near a gigabyte:

  ~ λ git clone  https://github.com/ocaml/opam-repository
  Cloning into 'opam-repository'...
  Receiving objects: 100% (316368/316368), 69.07 MiB | 5.70 MiB/s, 
  done.

  ~ λ du -hs opam-repository/
  562M	opam-repository/

Halp,

T G-R

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: 79-GiB opam checkout in ~/.cache/guix
  2019-11-18 22:58 79-GiB opam checkout in ~/.cache/guix Tobias Geerinckx-Rice
@ 2019-11-19  0:03 ` Bengt Richter
  0 siblings, 0 replies; 2+ messages in thread
From: Bengt Richter @ 2019-11-19  0:03 UTC (permalink / raw)
  To: Tobias Geerinckx-Rice; +Cc: Guix Devel

Hi Tobias,

On +2019-11-18 23:58:10 +0100, Tobias Geerinckx-Rice wrote:
> Auntie Guix,
> 
> My SSD hurts & my ~/.cache/guix feels funny:
> 
>  ~ λ du -hs ~/.cache/guix/checkouts/* | sort -h
>  560K	/home/nckx/.cache/guix/checkouts/hp4…
>  1.3M	/home/nckx/.cache/guix/checkouts/l74…
>  2.5M	/home/nckx/.cache/guix/checkouts/hep…
>  219M	/home/nckx/.cache/guix/checkouts/pjm…
>  79G	/home/nckx/.cache/guix/checkouts/f5u…
> 
> …wait, what the hell is that last one?
> 
>  ~ λ cat ~/.cache/guix/checkouts/f5u…/.git/config
>  [core]
> 	bare = false
> 	repositoryformatversion = 0
> 	filemode = true
> 	logallrefupdates = true
>  [remote "origin"]
> 	url = https://github.com/ocaml/opam-repository
> 	fetch = +refs/heads/*:refs/remotes/origin/*
> 
> I have no idea what this means or what has happened.  I don't remember
> running an opam importer recently, although I've probably run ‘guix refresh’
> on an opam package or so.
> 
> Still.
> 
> According to GitHub, the repository is only 70.9 *MiB* and when I clone it
> locally it's still nowhere near a gigabyte:
> 
>  ~ λ git clone  https://github.com/ocaml/opam-repository
>  Cloning into 'opam-repository'...
>  Receiving objects: 100% (316368/316368), 69.07 MiB | 5.70 MiB/s,  done.
> 
>  ~ λ du -hs opam-repository/
>  562M	opam-repository/
> 
> Halp,
> 
> T G-R

Did you possibly get recursion into a lot of unintended submodules?

What would you get if you cd into opam-repository above and did
per "man got-clone" below (cf. "This is equivalent to running ..."

    git submodule update --init --recursive

(i.e. with no <pathspec>, to get all submodules)

What is du -hs ../opam-repository after that finishes?


copied from man git-clone:
--8<---------------cut here---------------start------------->8---
	--recurse-submodules[=<pathspec]
	    After the clone is created, initialize and clone
	    submodules within based on the provided pathspec. If no
	    pathspec is provided, all submodules are initialized and
	    cloned. This option can be given multiple times for
	    pathspecs consisting of multiple entries. The resulting
	    clone has submodule.active set to the provided pathspec,
	    or "." (meaning all submodules) if no pathspec is
	    provided.

	    Submodules are initialized and cloned using their
	    default settings. This is equivalent to running git
	    submodule update --init --recursive <pathspec>
	    immediately after the clone is finished. This option is
	    ignored if the cloned repository does not have a
	    worktree/checkout (i.e. if any of --no-checkout/-n,
	    --bare, or --mirror is given)
--8<---------------cut here---------------end--------------->8---

HTH
-- 
Regards,
Bengt Richter

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-11-19  0:03 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-11-18 22:58 79-GiB opam checkout in ~/.cache/guix Tobias Geerinckx-Rice
2019-11-19  0:03 ` Bengt Richter

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).