From: Luis Ressel <aranea@aixah.de>
To: gentoo-dev@lists.gentoo.org
Cc: pr@gentoo.org
Subject: [gentoo-dev] News item: sys-apps/s6 ftrig ABI change
Date: Tue, 12 Mar 2019 01:01:13 +0100 [thread overview]
Message-ID: <20190312000113.nfkws52qhb24v3mk@deneb.skynet.aixah.de> (raw)
Hello,
here's a draft for a news item I'd like to publish before bumping
sys-apps/s6 to 2.8.0.0:
Title: sys-apps/s6 2.8 ftrig ABI change
Author: Luis Ressel <aranea@aixah.de>
Posted: 2019-03-??
Revision: 1
News-Item-Format: 2.0
Display-If-Installed: <sys-apps/s6-2.8.0.0
The 2.8 release of s6 includes a bugfix for the ftrig notification framework
which breaks the internal ABI. Thus 2.8 clients may not receive notifications
from a pre-2.8 server.
This affects the s6-ftrig-* tools as well as the service state
notifications provided by s6-supervise. If you rely on these (in
particular by using s6-svlisten/s6-svwait or s6-rc), freezes will ensue.
It is therefore recommended to shut down all s6 supervision trees before
upgrading to s6 2.8.0.0. This may not be an option if you use s6-svscan
as PID 1; in this case stop as many services as possible, perform the
upgrade and then reboot your system, killing all hanging
s6-svlisten/s6-svwait processes manually.
--
Cheers,
Luis Ressel
reply other threads:[~2019-03-12 0:01 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190312000113.nfkws52qhb24v3mk@deneb.skynet.aixah.de \
--to=aranea@aixah.de \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pr@gentoo.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