From: Tomas Volf <~@wolfsden.cz>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: help-guix@gnu.org
Subject: Re: Is a graft warranted here?
Date: Sat, 15 Jun 2024 10:15:52 +0200 [thread overview]
Message-ID: <Zm1NuLD3s8TDCxuc@ws> (raw)
In-Reply-To: <87v82b11t6.fsf@lease-up.com>
[-- Attachment #1: Type: text/plain, Size: 3124 bytes --]
On 2024-06-14 17:34:29 -0700, Felix Lechner wrote:
> Hi Tomas,
>
> Thank you for writing!
>
> On Sat, Jun 15 2024, Tomas Volf wrote:
>
> > Could you write bit more about how to reproduce it and what to look
> > for?
>
> My issue may be with 'guix shell'. Would you please run
>
> guix shell nyacc
>
> one time in order to get version 1.08.1 into your store and into your
> local profiles, and then run
>
> guix shell -f guix.scm
>
> on the package definition I sent. Sorry I forgot the module includes.
> Here they are part of a larger file, but the ones below should work.
Here is the output (the commit is current master at the time of testing):
$ guix time-machine -q --commit=43e102be746e5be11ddd9e1af9b65e3d8571d232 -- shell guile nyacc -- guile -c '(pk (@ (nyacc version) *nyacc-version*))'
;;; ("1.08.1")
$ guix time-machine -q --commit=43e102be746e5be11ddd9e1af9b65e3d8571d232 -- shell guile -f /tmp/guix.scm -- guile -c '(pk (@ (nyacc version) *nyacc-version*))'
The following derivation will be built:
/gnu/store/50q9n6as12h1ln9nlmb6ra4qr82lncjy-profile.drv
applying 2 grafts for nyacc-1.10-dev ...
building CA certificate bundle...
listing Emacs sub-directories...
building fonts directory...
building directory of Info manuals...
building profile with 2 packages...
;;; ("1.09.4")
With the /tmp/guix.scm being:
(use-modules
(gnu packages autotools)
(gnu packages guile)
(gnu packages guile-xyz)
(gnu packages linux)
(gnu packages mes)
(gnu packages pkg-config)
(gnu packages texinfo)
(gnu packages)
(guix build-system gnu)
(guix gexp)
(guix git-download)
((guix licenses) #:prefix license:)
(guix packages)
(guix utils))
(define-public nyacc/juix
(let* ((commit "41691b062b598a92549821879766e0ee48b635da")
(revision "0"))
(package
(inherit nyacc)
(name "nyacc")
(version "1.10-dev")
(source (origin
(method git-fetch)
(uri (git-reference
(url "https://git.savannah.nongnu.org/git/nyacc.git")
(commit commit)))
(file-name (git-file-name name version))
(sha256
(base32
"1fa88fix6avyazyiy4k70v9fzdkz1i0p99xnmxmq94j3wpc76y3j"))
(modules '((guix build utils)))
(snippet
'(substitute* "configure"
(("GUILE_GLOBAL_SITE=\\$prefix.*")
"GUILE_GLOBAL_SITE=\
$prefix/share/guile/site/$GUILE_EFFECTIVE_VERSION\n"))))))))
nyacc/juix
Even when I actually put your code into mes.scm it seems to work fine:
$ guix-dev-shell -- ./pre-inst-env guix shell guile nyacc -- guile -c '(pk (@ (nyacc version) *nyacc-version*))'
[..]
;;; ("1.09.4")
Sorry I could not reproduce :/
Have a nice day,
Tomas
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-06-15 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 23:27 Is a graft warranted here? Felix Lechner via
2024-06-14 23:49 ` Tomas Volf
2024-06-15 0:34 ` Felix Lechner via
2024-06-15 8:15 ` Tomas Volf [this message]
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=Zm1NuLD3s8TDCxuc@ws \
--to=~@wolfsden.cz \
--cc=felix.lechner@lease-up.com \
--cc=help-guix@gnu.org \
/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.
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).