all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dennis Mungai <dmngaie@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 22948@debbugs.gnu.org
Subject: bug#22948: Porting ocl-icd to guix fails because of ruby
Date: Thu, 10 Mar 2016 15:18:17 +0300	[thread overview]
Message-ID: <CAKKYfmF8xkmqqNEEz6DAv8zctTVxNf+9dDB0oyv5Y1LbJFiByQ@mail.gmail.com> (raw)
In-Reply-To: <87a8m7dbdm.fsf@gnu.org>

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

Hello,

And a small update:

After running the garbage collector, the problem went away (And saved me
about 20GBs under /gnu/store).

I'm suspecting this was a corrupt store.

On 9 March 2016 at 16:33, Ludovic Courtès <ludo@gnu.org> wrote:

> Dennis Mungai <dmngaie@gmail.com> skribis:
>
> > env TEMPDIR=/gnu/tmp GUIX_PACKAGE_PATH=../guix-bioinformatics
> > ./pre-inst-env guix build -K ocl-icd
>
> Note that setting TEMPDIR here (or even TMPDIR) has no effect, since
> it’s the ‘guix-daemon’ process, not ‘guix build’, that creates temporary
> files.
>
> > Error encountered:
> >
> > guix build: error: build failed: error parsing derivation
> > `/gnu/store/7f9hwk8v9vzghc93m93y94iibvcc3mvd-ruby-2.3.0.tar.xz.drv':
> > expected string `Derive(['
>
> Could you send the content of the file above?
>
> It looks like your store may be be corrupt.  Did you modify files by
> hand under /gnu/store?  This would void your warranty.  :-)
>
> Thanks,
> Ludo’.
>

[-- Attachment #2: Type: text/html, Size: 1462 bytes --]

  reply	other threads:[~2016-03-10 12:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 19:41 bug#22948: Porting ocl-icd to guix fails because of ruby Dennis Mungai
2016-03-09 13:33 ` Ludovic Courtès
2016-03-10 12:18   ` Dennis Mungai [this message]
2016-03-10 13:09     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKKYfmF8xkmqqNEEz6DAv8zctTVxNf+9dDB0oyv5Y1LbJFiByQ@mail.gmail.com \
    --to=dmngaie@gmail.com \
    --cc=22948@debbugs.gnu.org \
    --cc=ludo@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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.