unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Timothy Sample <samplet@ngyro.com>
Cc: swedebugia@riseup.net, 33755-done@debbugs.gnu.org
Subject: bug#33755: error: execlp: No such file or directory from guix environment
Date: Tue, 18 Dec 2018 10:05:12 +0100	[thread overview]
Message-ID: <87tvjbjjcn.fsf@gnu.org> (raw)
In-Reply-To: <875zvszrwd.fsf@ngyro.com> (Timothy Sample's message of "Sun, 16 Dec 2018 23:41:38 -0500")

Hi Timothy,

Timothy Sample <samplet@ngyro.com> skribis:

> Aha!  I didn’t know about “error-reporting-wrapper”.  I think this makes
> sense.  It fixes the same issue in the container script, too.  I’ve
> attached an updated patch.
>
> I had to modify “error-reporting-wrapper” to deal with the fact that
> “execlp” takes a variable number of arguments.  I tested it and it works
> for the old use-case as well as the new.  On whether or not it works
> stylistically, I defer to you.

I like it.  :-)

> From 428b80973026909c915e1f33d4509e82f66355e3 Mon Sep 17 00:00:00 2001
> From: Timothy Sample <samplet@ngyro.com>
> Date: Sun, 16 Dec 2018 23:12:13 -0500
> Subject: [PATCH] ui: Report file names in 'system-error' exceptions from
>  'execlp'.
>
> Fixes <https://bugs.gnu.org/33755>.
>
> * guix/ui.scm (apply-formals): New macro.
> (execlp): New error-reporting wrapper.

Applied, thank you!

Ludo’.

      reply	other threads:[~2018-12-18  9:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-15  7:09 bug#33755: error: execlp: No such file or directory from guix environment swedebugia
2018-12-15  9:40 ` Julien Lepiller
2018-12-15 18:18   ` Timothy Sample
2018-12-15 18:35     ` Timothy Sample
2018-12-15 19:38       ` Danny Milosavljevic
2018-12-16  4:26         ` Timothy Sample
2018-12-16 16:05           ` Ludovic Courtès
2018-12-17  4:41             ` Timothy Sample
2018-12-18  9:05               ` 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

  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=87tvjbjjcn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=33755-done@debbugs.gnu.org \
    --cc=samplet@ngyro.com \
    --cc=swedebugia@riseup.net \
    /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).