From: Mekeor Melire <mekeor@posteo.de>
To: help-guix@gnu.org
Subject: [DONE] `guix pull` leads an error while building guix-package-cache
Date: Mon, 21 Mar 2022 21:28:28 +0000 [thread overview]
Message-ID: <874k3ryouw.fsf@posteo.de> (raw)
In-Reply-To: <878rt3yy4m.fsf@posteo.de>
Sorry for the noise. Apparently, there was a bad package definition in
my custom channel. I realized that I'm much faster debugging and testing
my package with
- add package-name as expression at the end of package-file; and
- `guix package -f foo.scm` every time to test the file;
than with
- change file; commit it to the channel repo;
- `guix pull`;
- guix install package-name.
Anyways. Thank you.
2022-03-21 / 19:04 / mekeor@posteo.de:
> Hi Guix,
>
> when I run `guix pull`, it results in this error:
>
> \builder for `/gnu/store/…-guix-package-cache.drv' failed to produce output path `/gnu/store/…-guix-package-cache'
> build of /gnu/store/…-guix-package-cache.drv failed
> View build log at '/var/log/guix/drvs/di/…-guix-package-cache.drv.bz2'.
> cannot build derivation `/gnu/store/…-profile.drv': 1 dependencies couldn't be built
> guix pull: error: build of `/gnu/store/…-profile.drv' failed
>
> These are the error logs:
>
> (repl-version 0 1 1)
> Generating package cache for '/gnu/store/…-profile'...
> (exception unbound-variable (value #f) (value "Unbound variable: ~S") (value (gexp)) (value #f))
>
> What's wrong with my system?
>
> I also have a private, custom guix-channel. Its .git-directory got
> corrupted, so I had to remove it and re-initialize the repository. Could
> that be a reason for Guix to break? How can I repair my state?
>
> Thanks in advance.
prev parent reply other threads:[~2022-03-21 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 18:04 `guix pull` leads an error while building guix-package-cache Mekeor Melire
2022-03-21 21:28 ` Mekeor Melire [this message]
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=874k3ryouw.fsf@posteo.de \
--to=mekeor@posteo.de \
--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.
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.