unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: George Clemmer <myglc2@gmail.com>
Cc: 37789@debbugs.gnu.org
Subject: bug#37789: guix pull: error: You found a bug: the program
Date: Sat, 19 Oct 2019 22:09:04 +0200	[thread overview]
Message-ID: <87ftjov6ov.fsf@gnu.org> (raw)
In-Reply-To: <87bluczhc5.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 19 Oct 2019 21:05:30 +0200")

Ludovic Courtès <ludo@gnu.org> skribis:

>> The guix-configuration is unchanged since then. Shouldn't 'guix pull'
>> still work?
>
> It should work, yes.  What does ‘guix describe’ report?

Note that what you initially reported is not so much that ‘guix pull’
“doesn’t work” but rather that it failed to build ghostscript.

Could you send the tail of the log returned by:

  guix build --log-file /gnu/store/j5lp13iwcwnsdk545lgg1nh8kn4jdj3d-ghostscript-9.27.drv

Thanks,
Ludo’.

  parent reply	other threads:[~2019-10-19 20:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17 10:49 bug#37789: guix pull: error: You found a bug: the program my glc2
2019-10-17 14:58 ` Ludovic Courtès
2019-10-17 16:39   ` George Clemmer
2019-10-17 19:34     ` Ludovic Courtès
2019-10-18 14:57       ` George Clemmer
2019-10-19 19:05         ` Ludovic Courtès
2019-10-19 19:56           ` George Clemmer
2019-10-19 20:09           ` Ludovic Courtès [this message]
2019-10-21 21:00             ` George Clemmer
2019-10-21 21:21               ` George Clemmer
2019-10-23  9:59               ` Ludovic Courtès
2019-10-23 13:35                 ` George Clemmer
2020-06-09 23:12                 ` George Clemmer
2020-06-09 23:40                   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-06-10 14:48                   ` 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=87ftjov6ov.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=37789@debbugs.gnu.org \
    --cc=myglc2@gmail.com \
    /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).