unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Fulbert <fulbert@bluewin.ch>
Subject: Re: cleaning interrupted build "leftovers" ?
Date: Fri, 28 Aug 2020 13:03:42 +0200	[thread overview]
Message-ID: <20200828110342.GA16317@jurong> (raw)
In-Reply-To: <20200828103411.GA8514@bluewin.ch>

On Fri, Aug 28, 2020 at 12:34:11PM +0200, Fulbert wrote:
>   Yesterday, I interrupted (CTRL+C) the installation of
> linux-libre@5.8.5 when it was in build phase (substitute not
> available yet). Today, a new `guix system reconfigure` has
> found a substitute. I am wondering if, in this situation, my system
> has "leftovers" from the aborted build, that I would need to
> clean… and if so, {where,how} to find it ?! 

packages are normally built in /tmp, each package in its own subdirctory
guix-build-<package>. When interrupting the build with Ctrl-C, this
directory survives (and on most systems is deleted during the next reboot).

>   Based on the [attached] result of the following command, I
> suppose, but I am unsure.
> ----
> $ sudo find -L /var/guix /gnu/store -name "*linux-libre-5.8.5*" 2> /dev/null
>   1228101      4 dr-xr-xr-x   6 root     root         4096 jan  1  1970 /var/guix/profiles/system/kernel/share/doc/linux-libre-5.8.5

This looks like it is part of your successful upgrade of the system with
a substitute.
$ ls -l /var/guix/profiles
shows links to profiles in /gnu/store (and if space runs out, these can
be removed by deleting profiles and "guix gc").

Andreas



  parent reply	other threads:[~2020-08-28 11:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28 10:34 cleaning interrupted build "leftovers" ? Fulbert
2020-08-28 10:58 ` Ricardo Wurmus
2020-08-28 11:03 ` Andreas Enge [this message]
2020-08-28 11:11 ` Fulbert

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=20200828110342.GA16317@jurong \
    --to=andreas@enge.fr \
    --cc=fulbert@bluewin.ch \
    /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).