From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>,
"Maxime Devos" <maximedevos@telenet.be>,
"Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>,
28510@debbugs.gnu.org
Subject: bug#28510: crash: guix build -S foo --with-source=bla
Date: Tue, 20 Sep 2022 21:42:41 +0200 [thread overview]
Message-ID: <87h7113k9a.fsf@jpoiret.xyz> (raw)
In-Reply-To: <86a66u0xhr.fsf@gmail.com>
Hi Simon,
zimoun <zimon.toutoune@gmail.com> writes:
> Well, I would add an error handler; as proposed [1]. :-) Because does
> “guix build foo --source --with-source=bla” make sense? What is the
> use-case for such command?
My bad, I didn't see the previous discussion on the subject. To me, the
lack of generality would be unexpected: if I have a package with a
source, I expect to be able to get that source, whatever the source may
be. Maxime's minimal example shows that it could happen for a variety
of different reasons, not just a --with-source= flag. I don't know what
a proper fix for it would be though, since we're passing things around
that we pretend are derivations but are not, and in many places.
Best,
--
Josselin Poiret
next prev parent reply other threads:[~2022-09-20 23:10 UTC|newest]
Thread overview: 9+ 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 [this message]
2022-10-07 8:41 ` jeremy
2022-10-08 13:52 ` zimoun
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=87h7113k9a.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=28510@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=jeremy@korwin-zmijowski.fr \
--cc=maximedevos@telenet.be \
--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).