From: "Ludovic Courtès" <ludo@gnu.org>
To: Simon Josefsson via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org>
Cc: Simon Josefsson <simon@josefsson.org>,
Vagrant Cascadian <vagrant@debian.org>
Subject: Re: Shepherd in Debian
Date: Sun, 15 Dec 2024 01:01:52 +0100 [thread overview]
Message-ID: <877c81ke4v.fsf@gnu.org> (raw)
In-Reply-To: <87o71g7ugu.fsf@kaka.sjd.se> (Simon Josefsson via's message of "Thu, 12 Dec 2024 17:10:41 +0100")
Hi Simon,
Simon Josefsson via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org> skribis:
> I've packaged Shepherd 1.0.0 and guile-fibers 1.3.1 for Debian, and they
> are in the NEW queue pending copyright review. Meanwhile you can test
> the Salsa amd64 and i386 builds like this:
Nice!
> The halt, reboot and shutdown tools are not installed as that felt like
> a bad idea.
That would have been fun. :-)
> Btw, running 'herd --help' prints a lot of warnings like below. Any
> ideas where these come from and/or how to silence them? Salsa used
> Guile 3.0.9 and my laptop has Guile 3.0.7, if that matters.
>
> ;;; WARNING: loading compiled file /usr/lib/x86_64-linux-gnu/guile/3.0/site-ccache/shepherd/scripts/herd.go failed:
> ;;; In procedure load-thunk-from-memory: incompatible bytecode version
That indicates a discrepancy between the Guile used to build the
Shepherd and the one used at run time. Object files built by 3.0.9 (as
is the case here) cannot be understood by 3.0.7.
How’s that handled for other Guile packages in Debian? Vagrant must
know. :-)
Ludo’.
next prev parent reply other threads:[~2024-12-15 0:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 16:10 Shepherd in Debian Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2024-12-12 17:25 ` Tobias Alexandra Platen
2024-12-15 0:01 ` Ludovic Courtès [this message]
2024-12-15 1:06 ` Simon Josefsson via Development of GNU Guix and the GNU System distribution.
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=877c81ke4v.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=simon@josefsson.org \
--cc=vagrant@debian.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.
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).