From: elaexuotee@wilsonb.com
To: "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: help-guix@gnu.org
Subject: Re: Running shepherd as user: incompatible bytecode version
Date: Sun, 12 Feb 2023 17:09:04 +0900 [thread overview]
Message-ID: <3V2YSLNBKGZYC.3PVDUZLZHAXRA@wilsonb.com> (raw)
In-Reply-To: <e0a9437beddb127f4c9ee115c649bcfaac6cc694.camel@zaclys.net>
Hello Léo,
> I get the same issue, the shepherd package uses GNU Guile 3.0.2 and GNU
> Guix provides GNU Guile 3.0.5 under the 'guile' package specification
> name.
>
> I am not sure this is the cause, since shepherd is wrapped to use GNU
> Guile 3.0.2.
>
> I am also still looking for a solution.
>
> Léo
After guiving Shepherd user services a quick poke again, just now, I noticed
that the original issue isn't occurring. It looks the fix for
https://issues.guix.gnu.org/58631, introduced last November makes shepherd use
guile-3.0-latest, bringing it in line with guix.
prev parent reply other threads:[~2023-02-12 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 15:39 Running shepherd as user: incompatible bytecode version elaexuotee
2021-04-15 22:19 ` Léo Le Bouter
2021-04-18 16:49 ` elaexuotee
2023-02-12 8:09 ` elaexuotee [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=3V2YSLNBKGZYC.3PVDUZLZHAXRA@wilsonb.com \
--to=elaexuotee@wilsonb.com \
--cc=help-guix@gnu.org \
--cc=lle-bout@zaclys.net \
/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).