From: Jelle Licht <jlicht@fsfe.org>
To: 30896@debbugs.gnu.org
Subject: bug#30896: Guix pull problems on armhf
Date: Wed, 21 Mar 2018 20:59:01 +0100 [thread overview]
Message-ID: <87muz1kxoa.fsf@fsfe.org> (raw)
I have been running the binary Guix installation on top of Armbian
on my
Rockchip RK3288 (armhf) based computing platform.
Up till about ~8 days ago, guix pull worked as intended. Recently,
running guix pull leads to the following error message
`./guix/build/pull.scm:44:20: ./guix/build/pull.scm:44:20: Throw
to key
`match-error' with args `("match" "no matching pattern"' [1]
I already checked that re{moving,naming}
`$HOME/.config/guix/latest'
does not change anything. Neither does running `./pre-inst-env
guix
pull' from a git checkout.
[1]: For the full log, see: https://paste.debian.net/1015219/
--
Jelle Licht
next reply other threads:[~2018-03-21 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 19:59 Jelle Licht [this message]
2021-09-16 7:36 ` bug#30896: Guix pull problems on armhf zimoun
2021-11-24 23:54 ` 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=87muz1kxoa.fsf@fsfe.org \
--to=jlicht@fsfe.org \
--cc=30896@debbugs.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 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).