From: "Laurent Bercot" <ska-skaware@skarnet.org>
To: "skaware@list.skarnet.org" <skaware@list.skarnet.org>,
"supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: [announce] skarnet.org October 2024 update
Date: Wed, 09 Oct 2024 17:21:14 +0000 [thread overview]
Message-ID: <emdff5dfe4-2609-4bf4-b0f6-085166c77d64@c0398fa5.com> (raw)
Hello,
New versions of all the skarnet.org packages are available. This is
a light update, focused on bugfixes, quality of life changes, and
small default policy changes. Upgrade at your convenience.
skalibs-2.14.3.0 (minor)
nsss-0.2.0.5 (release)
utmps-0.1.2.3 (release)
execline-2.9.6.1 (release)
s6-2.13.1.0 (minor)
s6-rc-0.5.5.0 (minor)
s6-linux-init-1.1.2.1 (release)
s6-portable-utils-2.3.0.4 (release)
s6-linux-utils-2.6.2.1 (release)
s6-dns-2.4.0.0 (major)
s6-networking-2.7.0.4 (release)
mdevd-0.1.6.5 (release)
smtpd-starttls-proxy-0.0.1.5 (release)
tipidee-0.0.5.1 (release)
shibari-0.0.1.2 (release)
bcnm-0.0.1.8 (release)
dnsfunnel-0.0.2.0 (minor)
apaste-0.0.2.1 (release)
Some details below. If there are no details for a package, the
release only contains bugfixes and/or code cleanups.
* General
-------
- All packages that export static libraries now install them in
/usr/lib by default. This is to align with what most distributions
do when packaging.
- If you're using git: the main branch for all packages is now
called "main".
* skalibs-2.14.3.0
----------------
- Important bugfixes for some of the software stack.
- New function: fork_newpid(), forking a process in a new pid
namespace on Linux (and returning -1 ENOSYS on other systems).
- QoL: IOPAUSE_EXCEPT will now always trigger IOPAUSE_READ or
IOPAUSE_WRITE as well, which means error handling before the IO
primitive is now unnecessary.
https://skarnet.org/software/skalibs/
git://git.skarnet.org/skalibs
* s6-2.13.1.0
-----------
- Some of the bugfixes are pretty impactful, and it is recommended
to upgrade (including the skalibs upgrade). You don't need to
restart your services or supervision trees if you haven't noticed
anything wrong.
- s6-supervise now supports a new file in the service directory:
flag-newpidns. If this file is present at service spawning time,
the process will be started in a new PID namespace. (Linux only;
on other systems, the service will fail to start if the file exists.)
https://skarnet.org/software/s6/
git://git.skarnet.org/s6
* s6-rc-0.5.5.0
-------------
- This is a minor update because a bugfix required adding a new
public API, s6rc_livedir_canon(). Apart from that, the change is
purely bugfixes.
- You do not need to recompile your service databases.
https://skarnet.org/software/s6-rc/
git://git.skarnet.org/s6-rc
* s6-dns-2.4.0.0
--------------
- This is a major update because a function was factorized in skalibs,
and the libs6dns implementation (s6dns_minineststring_read()) was
removed.
- A new function, s6dns_engine_query(), was also added.
- Higher debug levels in s6-dnsq and s6-dnsqr can now dump
received packets.
https://skarnet.org/software/s6-dns/
git://git.skarnet.org/s6-dns
* s6-networking-2.7.0.4
---------------------
- If you're using s6-tcpserver-access with IPv6 addresses, you
should upgrade the s6 package (and rebuild s6-networking if you're
linking it statically against libs6).
- QoL: s6-tcpclient now does not qualify its argument by default
(the default changes from -n to -N), to avoid confusion when users
give a fqdn without a final dot.
https://skarnet.org/software/s6-networking/
git://git.skarnet.org/s6-networking
* dnsfunnel-0.0.2.0
-----------------
- dnsfunneld can now listen to IPv6 addresses.
https://skarnet.org/software/dnsfunnel/
git://git.skarnet.org/dnsfunnel
Enjoy,
Bug-reports welcome.
--
Laurent
next reply other threads:[~2024-10-09 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 17:21 Laurent Bercot [this message]
2024-10-11 0:33 ` Alexis
2024-10-15 0:45 Alexis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=emdff5dfe4-2609-4bf4-b0f6-085166c77d64@c0398fa5.com \
--to=ska-skaware@skarnet.org \
--cc=skaware@list.skarnet.org \
--cc=supervision@list.skarnet.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 NNTP newsgroup(s).