From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel@gnu.org, guile-sources@gnu.org, guile-user@gnu.org,
info-gnu@gnu.org
Subject: GNU Shepherd 0.10.5 released
Date: Wed, 26 Jun 2024 16:30:50 +0200 [thread overview]
Message-ID: <8734ozbwth.fsf@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3899 bytes --]
We are pleased to announce the GNU Shepherd version 0.10.5, a bug-fix
release of the 0.10.x series, representing 5 commits over 3 months.
The 0.10.x series is a major overhaul towards 1.0. The current ‘devel’
branch provides new features and significant user interface
improvements; it will become 1.0 in the coming weeks or months.
• About
The GNU Shepherd is a service manager written in Guile that looks
after the herd of daemons running on the system. It can be used as an
“init” system (PID 1) and also by unprivileged users to manage
per-user daemons—e.g., tor, privoxy, mcron. It supports several
daemon startup mechanisms, including inetd and systemd-style socket
activation. The GNU Shepherd is configured in Guile Scheme and can be
extended in the same language. It builds on a simple memory-safe and
callback-free programming model.
The GNU Shepherd is developed jointly with the GNU Guix project; it is
used as the init system of Guix, GNU’s advanced GNU/Linux distribution.
https://www.gnu.org/software/shepherd/
• Download
For a summary of changes and contributors, see:
https://git.sv.gnu.org/gitweb/?p=shepherd.git;a=shortlog;h=v0.10.5
or run this command from a git-cloned shepherd directory:
git shortlog v0.10.4..v0.10.5
Here are the compressed sources and a GPG detached signature:
https://ftp.gnu.org/gnu/shepherd/shepherd-0.10.5.tar.gz
https://ftp.gnu.org/gnu/shepherd/shepherd-0.10.5.tar.gz.sig
Use a mirror for higher download bandwidth:
https://ftpmirror.gnu.org/shepherd/shepherd-0.10.5.tar.gz
https://ftpmirror.gnu.org/shepherd/shepherd-0.10.5.tar.gz.sig
Here are the SHA1 and SHA256 checksums:
5a00d408660ba02098f6db75f6192c1ee8d1d5c3 shepherd-0.10.5.tar.gz
ncg4eLxPnCIoHU7mwn4SgzT4TkFB6UiSw7nkUnGygEw= shepherd-0.10.5.tar.gz
Verify the base64 SHA256 checksum with cksum -a sha256 --check
from coreutils-9.2 or OpenBSD's cksum since 2007.
Use a .sig file to verify that the corresponding file (without the
.sig suffix) is intact. First, be sure to download both the .sig file
and the corresponding tarball. Then, run a command like this:
gpg --verify shepherd-0.10.5.tar.gz.sig
The signature should match the fingerprint of the following key:
pub rsa4096 2014-08-11 [SC]
3CE4 6455 8A84 FDC6 9DB4 0CFB 090B 1199 3D9A EBB5
uid [ undef ] Ludovic Courtès <ludo@gnu.org>
uid [ undef ] Ludovic Courtès <ludo@chbouib.org>
uid [ undef ] Ludovic Courtès (Inria) <ludovic.courtes@inria.fr>
If that command fails because you don't have the required public key,
or that public key has expired, try the following commands to retrieve
or refresh it, and then rerun the 'gpg --verify' command.
gpg --recv-keys 3CE464558A84FDC69DB40CFB090B11993D9AEBB5
As a last resort to find the key, you can try the official GNU
keyring:
wget -q https://ftp.gnu.org/gnu/gnu-keyring.gpg
gpg --keyring gnu-keyring.gpg --verify shepherd-0.10.5.tar.gz.sig
This release was bootstrapped with the following tools:
Autoconf 2.71
Automake 1.16.5
Gettext 0.21
Makeinfo 7.1
• Changes since version 0.10.4 (excerpt from the NEWS file)
** ‘herd unload root SERVICE’ no longer hangs when there’s a replacement
(<https://issues.guix.gnu.org/71478>)
It used to be that, for a running service S that has a replacement registered,
‘herd unload root S’ would hang shepherd, making it totally unresponsive—‘herd
status’, ‘halt’, etc. would hang forever, and inetd-style services would no
longer start, etc. This is now fixed.
Please report bugs to bug-guix@gnu.org.
Join guix-devel@gnu.org for discussions.
Ludovic, on behalf of the Shepherd herd.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]
reply other threads:[~2024-06-26 14:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8734ozbwth.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-sources@gnu.org \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.org \
--cc=info-gnu@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).