[Bug 282021] sysutils/s6: some notification-fd values are mistakenly invalid on FreeBSD (regression)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282021

            Bug ID: 282021
           Summary: sysutils/s6: some notification-fd values are
                    mistakenly invalid on FreeBSD (regression)
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: sg@redu.cx
                CC: crest@rlwinm.de
             Flags: maintainer-feedback?(crest@rlwinm.de)
                CC: crest@rlwinm.de

Hello,

#279116 bumped sysutils/s6 from 2.11.3.2 to 2.12.0.4.  Unfortunately, this
pulled in a new upstream bug that manifests on FreeBSD but not on (most?) other
contemporary Unices -- and so it slipped through the cracks.  Briefly, some
notification-fd values that were valid in s6 2.11.3.2 became invalid in
2.12.0.4 by mistake.  Users with an impacted configuration would observe a
complete failure of their supervision trees.

More details can be found in the upstream bug report.
https://skarnet.org/lists/supervision/3171.html

----
# cat log/notification-fd 
6
# cat log/run
#!/bin/sh
exec s6-log -d 6 n2 s16384 t ./data
----

The configuration above reproduces the problem on s6 2.12.0.4 for me.

This problem was addressed in the latest respective releases of s6 and skalibs.
 Upstream cut releases earlier this week.

If you would prefer to backport a minimal patch, I think this should do it:
https://git.skarnet.org/cgi-bin/cgit.cgi/skalibs/commit/?id=a7973043c92dc0f9d083e600142a47ce6dd1c9f6

(This is technically a bug in devel/skalibs, though I figured any interested
users would search for sysutils/s6 in bugzilla.)

Many thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.