all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Chad Walstrom <chewie@wookimus.net>,
	Leo Famulari <leo@famulari.name>, Mark H Weaver <mhw@netris.org>,
	Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 34995-done@debbugs.gnu.org
Subject: bug#34995: `guix pull` crash on commit 69cae3d33
Date: Tue, 26 Mar 2019 10:40:37 +0100	[thread overview]
Message-ID: <87tvfqht2i.fsf@gnu.org> (raw)
In-Reply-To: <87imw6s2u5.fsf@wookimus.net> (Chad Walstrom's message of "Mon, 25 Mar 2019 22:59:32 -0500")

Hello,

Chad Walstrom <chewie@wookimus.net> skribis:

> ./gnu/packages/bootstrap.scm:150:4: In procedure inputs:
> Wrong number of arguments to #<procedure inputs (x)>
> guix pull: error: You found a bug: the program '/gnu/store/dml4spg4jl3nqqqgsw76pj74bash1h8h-compute-guix-derivation'
> failed to compute the derivation for Guix (version: "6c177f6140cba250ad68c5a83c312f395b6e48b4"; system: "x86_64-linux";
> host version: "0.16.0"; pull-version: 1).
> Please report it by email to <bug-guix@gnu.org>.

This bug was introduced about 11 hours ago when I pushed
abd4d6b33dba4de228e90ad15a8efb456fcf7b6e.

It’s due to an excess of confidence and insufficient testing on my side
(I hadn’t rebuilt the package modules locally, so those modules were
still using the old ABI and everything was fine); my apologies for the
breakage.

That also revealed an abstraction leakage I was unaware of:

  https://issues.guix.info/issue/34999

Thank you all for reporting the issue!

Ludo’.

      reply	other threads:[~2019-03-26  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26  1:27 bug#34995: `guix pull` crash on commit 69cae3d33 Leo Famulari
2019-03-26  3:03 ` Mark H Weaver
2019-03-26  3:50   ` Mark H Weaver
2019-03-26  3:59 ` Chad Walstrom
2019-03-26  9:40   ` Ludovic Courtès [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=87tvfqht2i.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=34995-done@debbugs.gnu.org \
    --cc=chewie@wookimus.net \
    --cc=konrad.hinsen@fastmail.net \
    --cc=leo@famulari.name \
    --cc=mhw@netris.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.