unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: John Kehayias via Bug reports for GNU Guix <bug-guix@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 58861@debbugs.gnu.org
Subject: bug#58861: guix shell emulate-fhs option can have wrong glibc package
Date: Wed, 02 Nov 2022 15:50:02 +0000	[thread overview]
Message-ID: <87y1st73vk.fsf@protonmail.com> (raw)
In-Reply-To: <87cza5frq6.fsf@gmail.com>

Hi simon and Ludo’,

Before I forget, nckx helpfully pointed out that I linked to the wrong commit, which made this all the more confusing. The correct commit is

<https://git.savannah.gnu.org/cgit/guix.git/commit/?id=8b192c5550213911f930594f4fd7386f36618237>

On Wed, Nov 02, 2022 at 01:47 PM, zimoun wrote:

> Hi,
>
> On sam., 29 oct. 2022 at 05:31, John Kehayias via Bug reports for GNU Guix
> <bug-guix@gnu.org> wrote:
>
>> --8<---------------cut here---------------start------------->8---
>> ❯ guix shell -CFD hello coreutils
>
>> ❯ guix shell -CD hello -F coreutils
>> --8<---------------cut here---------------end--------------->8---
>
> Unrelated, “guix package” provides some ’%actions’ and as reported in
> [1], the command-line order matters – when it should not be.  Maybe, as
> proposed in [1], “guix shell” could process a « plan » with always the
> same order, whatever the command-line order is.
>
> 1: <http://issues.guix.gnu.org/issue/50473>
>

Thanks, I'll take a look. Seems like we may want to have a more systematic method here.





  reply	other threads:[~2022-11-02 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-29  5:31 bug#58861: guix shell emulate-fhs option can have wrong glibc package John Kehayias via Bug reports for GNU Guix
2022-11-02 12:47 ` zimoun
2022-11-02 15:50   ` John Kehayias via Bug reports for GNU Guix [this message]
2022-11-02 15:50 ` Ludovic Courtès
2022-11-03 18:50   ` bug#58861: [PATCH] shell: Fix '--emulate-fhs' sometimes not including 'glibc-for-fhs' John Kehayias via Bug reports for GNU Guix
2022-11-06 11:18     ` 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=87y1st73vk.fsf@protonmail.com \
    --to=bug-guix@gnu.org \
    --cc=58861@debbugs.gnu.org \
    --cc=john.kehayias@protonmail.com \
    --cc=ludo@gnu.org \
    --cc=zimon.toutoune@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).