From: Felix Lechner via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 64858@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Felix Lechner" <felix.lechner@lease-up.com>,
"Pierre-Henry Fröhring" <phfrohring@deeplinks.com>
Subject: bug#64858: [PATCH] In 'guix shell', discard ad-hoc profile when 'guix.scm' file is newer. (Closes: #64858)
Date: Sun, 19 Nov 2023 21:12:36 -0800 [thread overview]
Message-ID: <9b178dff2dec09ca8af96fae54d5519c6d1cf1a4.1700457155.git.felix.lechner@lease-up.com> (raw)
In-Reply-To: <CAP84DVVaUGBugE3Xzo-A6noBAO=2kjZnRSrEeC+BFuOfpciQJA@mail.gmail.com>
Fixes a bug that prevents rebuilds for folks who use 'guix shell' repeatedly
to refine a package declaration located in a 'guix.scm' file.
The mtime of 'guix.scm' is never evaluated because 'file' is #f here and the
code path taken always returns 0 as the purported mtime.
https://github.com/guix-mirror/guix/blob/71b92466430acb8c91841522dc0eb7d766af4388/guix/scripts/shell.scm#L390
In the consuming code, the 'timestamp' is always less than the mtime of the
profile in the multi-line AND-ed conditional here:
https://github.com/guix-mirror/guix/blob/71b92466430acb8c91841522dc0eb7d766af4388/guix/scripts/shell.scm#L250
As a result, outdated ad-hoc profiles are always reused unless they are
expressly deleted via:
rm ~/.cache/guix/profiles/*
The bug was potentially introduced in commit c42b7baf when 'package was
transformed to 'ad-hoc-package without also changing the line in this commit.
A minimal reproducer can be found here:
https://codeberg.org/lechner/shell-bug
---
Hi Ludo'
> ‘guix shell’ caches based on the mtime of ‘guix.scm’
That's how is should work, but it doesn't as explained above. Here is
a patch.
Please adjust the commit message to your liking. Thanks!
Kind regards
Felix
guix/scripts/shell.scm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/guix/scripts/shell.scm b/guix/scripts/shell.scm
index 10ea110fee..d29367c8ee 100644
--- a/guix/scripts/shell.scm
+++ b/guix/scripts/shell.scm
@@ -398,7 +398,7 @@ (define (key->file key)
(values #f #f)))
((('nesting? . #t) . rest)
(loop rest system file (append specs '("nested guix"))))
- ((('load . ('package candidate)) . rest)
+ ((('load . ('ad-hoc-package candidate)) . rest)
(if (and (not file) (null? specs))
(loop rest system candidate specs)
(values #f #f)))
base-commit: 71b92466430acb8c91841522dc0eb7d766af4388
--
2.41.0
next prev parent reply other threads:[~2023-11-20 5:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 14:01 bug#64858: ~guix shell -C -f guix.scm …~ should not always need ~--rebuild-cache~ option to build the expected environment Pierre-Henry Fröhring
2023-10-12 15:25 ` Ludovic Courtès
2023-11-20 5:12 ` Felix Lechner via Bug reports for GNU Guix [this message]
2023-11-22 22:59 ` Ludovic Courtès
2023-11-23 0:38 ` Felix Lechner via Bug reports for GNU Guix
2023-11-26 4:17 ` Felix Lechner via Bug reports for GNU Guix
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=9b178dff2dec09ca8af96fae54d5519c6d1cf1a4.1700457155.git.felix.lechner@lease-up.com \
--to=bug-guix@gnu.org \
--cc=64858@debbugs.gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=ludo@gnu.org \
--cc=phfrohring@deeplinks.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).