unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Vincent Legoll <vincent.legoll@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 28510@debbugs.gnu.org
Subject: bug#28510: crash: guix build -S foo --with-source=bla
Date: Wed, 10 Jul 2024 20:28:17 +0000	[thread overview]
Message-ID: <CAEwRq=rMa2tR=q_uzXzvE=jw_B92Y6s+p2f6N15fyt1+pfDXhg@mail.gmail.com> (raw)
In-Reply-To: <8734ohgksb.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 638 bytes --]

Hello Simon,

On Wed, Jul 10, 2024 at 6:40 PM Simon Tournier <zimon.toutoune@gmail.com>
wrote:

> I removed the tag easy.


Thanks


> Well, I still think it’s an easy fix because to
> me the issue is not the failure of “guix build --source foo
> --with-source=bar” but the poor error handling.  However, if the aim to
> be able to pass such command-line, then indeed that’s not easy because
> it’s about some guarantee that the transformation is sound and that’s
> hard for the generic case, IMHO.
>

Well let's hope few such easy bugs linger for so long without being fixed
;-)

-- 
Vincent Legoll

[-- Attachment #2: Type: text/html, Size: 1250 bytes --]

  reply	other threads:[~2024-07-10 20:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 12:09 bug#28510: crash: guix build -S foo --with-source=bla Ricardo Wurmus
2021-02-25  0:34 ` zimoun
2022-09-19 17:38 ` Jérémy Korwin-Zmijowski
2022-09-19 18:44   ` Maxime Devos
2022-09-20  9:19     ` Josselin Poiret via Bug reports for GNU Guix
2022-09-20 17:25       ` zimoun
2022-09-20 19:42         ` Josselin Poiret via Bug reports for GNU Guix
2022-10-07  8:41           ` jeremy
2022-10-08 13:52             ` zimoun
2024-06-22 16:54 ` Vincent Legoll
2024-06-22 18:27   ` Vincent Legoll
2024-07-10 18:32   ` Simon Tournier
2024-07-10 20:28     ` Vincent Legoll [this message]
     [not found] <864kh0b4d2.fsf@gmail.com>
2024-07-10 18:26 ` Simon Tournier

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='CAEwRq=rMa2tR=q_uzXzvE=jw_B92Y6s+p2f6N15fyt1+pfDXhg@mail.gmail.com' \
    --to=vincent.legoll@gmail.com \
    --cc=28510@debbugs.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).