unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Maxime Devos <maximedevos@telenet.be>, 56289@debbugs.gnu.org
Subject: bug#56289: "guix shell -f guix2.scm" fails always
Date: Wed, 29 Jun 2022 11:22:57 +0200	[thread overview]
Message-ID: <823572af8921c9b7b1468ace6d248eb5f4bbee68.camel@ist.tugraz.at> (raw)
In-Reply-To: <cfdd155d4c1cfffcfb6344aa7d27b2a15aba84e4.camel@telenet.be>

Am Mittwoch, dem 29.06.2022 um 11:10 +0200 schrieb Maxime Devos:
> Liliana Marie Prikler schreef op wo 29-06-2022 om 08:19 [+0200]:
> > > Looks like "-f" is ignored entirely?
> > Have you tried specifying a file that actually contains a package
> > (not a manifest)?
> 
> None of the examples contain a manifest, oops-guix.scm actually
> contains a list of packages as mentioned previously (*).
My bad, I read that as specifications->manifest.  Note that for
specifications->package, you could simply specify hello on the command
line.

Having tested your file now, I can say that guix shell builds hello as
expected, whereas with specifications->manifest, it produces a lovely
backtrace (which is more or less what one ought to expect).

> And the exact same thing happens if a package is used instead of a
> list of packages.
One thing to check here is whether a cache might be interfering.  I
think it is an already known bug, that the file itself is not key in
the cache, which you can work around by specifying --rebuild-cache.

Cheers




  reply	other threads:[~2022-06-29  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 20:47 bug#56289: "guix shell -f guix2.scm" fails always Maxime Devos
2022-06-29  6:19 ` Liliana Marie Prikler
2022-06-29  9:10   ` Maxime Devos
2022-06-29  9:22     ` Liliana Marie Prikler [this message]
2022-06-29  9:40       ` Maxime Devos
2022-06-29  9:49         ` Liliana Marie Prikler

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=823572af8921c9b7b1468ace6d248eb5f4bbee68.camel@ist.tugraz.at \
    --to=liliana.prikler@ist.tugraz.at \
    --cc=56289@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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).