unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: "Ludovic Courtès" <ludo@gnu.org>, "Leo Famulari" <leo@famulari.name>
Cc: 27450@debbugs.gnu.org
Subject: bug#27450: guix pull failed updating guix
Date: Thu, 22 Jun 2017 23:09:44 +0200	[thread overview]
Message-ID: <84551531-620c-3881-abcb-9fd10200200a@web.de> (raw)
In-Reply-To: <87d19vpwbu.fsf@gnu.org>

Am 22.06.2017 um 23:05 schrieb Ludovic Courtès:
> Leo Famulari <leo@famulari.name> skribis:
> 
>> On Thu, Jun 22, 2017 at 06:20:54PM +0200, Jonathan Brielmaier wrote:
>>> copying and compiling to
>>> '/gnu/store/ld6h1fc696q6iaxi9pax0khnm747hvgi-guix-latest' with Guile
>>> 2.0.12...
>>> loading...	 12.6% of 605 filesice-9/psyntax.scm:3084:32: In procedure
>>> #<procedure 4f831a0 (k filename)>:
>>> ice-9/psyntax.scm:3084:32: Syntax error:
>>> bytestructures/guile/base.scm:8:19: include-from-path: file not found in
>>> path in subform "bytestructures/r7/base.exports.sld" of
>>> (include-from-path "bytestructures/r7/base.exports.sld")
>>> builder for
>>> `/gnu/store/lh7ja8hk54rlx7q3hrch6726cgrsqr8j-guix-latest.drv' failed
>>> with exit code 1
>>> guix pull: error: build failed: build of
>>> `/gnu/store/lh7ja8hk54rlx7q3hrch6726cgrsqr8j-guix-latest.drv' failed
>>> $ guix --version
>>> guix (GNU Guix) 20170303.14
>>>
>>> guile-version: 2.0.12
>>
>> This Guix was a bit old (from March 2017) and was using Guile 2.0
>> instead of Guile 2.2.
>>
>> I'm not sure, but I'd guess the issue is related to the recent addition
>> of a dependency on guile-bytestructures [0].
>>
>> [0]
>> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=19c90e5f697bbf1be5ea3a7b4f5fe712d77070a1
> 
> The problem is that there was a time window in March where
> ‘guile-bytestructures’ was broken as can be seen above.  This prevents
> upgrade here.  :-/
> 
> The workaround would be to first upgrade to the commit before the one
> you gave:
> 
>   guix pull \
>     --url=https://git.savannah.gnu.org/cgit/guix.git/snapshot/6fe5c49ab487154074eaab2ef80e9a2f8163320c.tar.gz
> 
> and then upgrade again:
> 
>   guix pull
> 
> Jonathan, are you able to confirm that this works or did you work around
> it differently already?
Sadly I can't confirm if this work around works because I reinstalled
guix (I removed the broken one and did a clean new 0.13 installation).

Next time I'll wait until the mailing list gives me the right commit :)

Jonathan

  reply	other threads:[~2017-06-22 21:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22 16:20 bug#27450: guix pull failed updating guix Jonathan Brielmaier
2017-06-22 18:27 ` Leo Famulari
2017-06-22 21:05   ` Ludovic Courtès
2017-06-22 21:09     ` Jonathan Brielmaier [this message]
2017-06-23  9:29       ` 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

  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=84551531-620c-3881-abcb-9fd10200200a@web.de \
    --to=jonathan.brielmaier@web.de \
    --cc=27450@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --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 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).