Heads up: lua-posix 36.1 headed to Rawhide
by Michel Alexandre Salim
Dear all,
Now that F38 is branched, it's probably a good time to upgrade lua-
posix from 35.1 to 36.1.
Packages potentially affected:
❯ rpmdistro-repoquery fedora rawhide --whatrequires lua-posix
Last metadata expiration check: 0:02:18 ago on Thu Feb 9 13:15:29
2023.
Lmod-0:8.7.18-1.fc38.x86_64
copy-jdk-configs-0:4.1-2.fc38.noarch
lua-readline-0:3.2-2.fc38.x86_64
There are some breaking changes in 36.0, so I'm going to only update in
Rawhide and we can revisit if we need to update in 38 and stable
branches later, but I tend towards keeping them at 35.1 unless there's
a major issue we can't fix without upgrading.
https://github.com/luaposix/luaposix/releases
Incompatible Changes
posix.spawn always returns integer, string whether fork fails
immediately, or whatever waiting for the spawned process reports. When
the second result value is "exited", the first is the exit status; for
"killed" or "stopped" second value, the first is the signal number that
caused it; otherwise first the errno error number, followed by the
associated error string.
The documentation for posix.spawn has always been wrong up until
now, but this small change to simplify the returned results will
require checking whether the second result value is "exited", "killed",
"stopped" or any other string before interpreting the first result...
which was also necessary in prior versions too, but now the
interpretion of non-zero status by clients is less messy and somewhat
compatible with the happy path of using previous releases.
Argument type errors for posix.sys.msg.msgctl,
posix.sys.resource.setrlimit, posix.sys.socket.bind,
posix.sys.socket.connect, posix.sys.socket.getaddrinfo,
posix.sys.socket.sendto and posix.time.nanosleep all use "integer" in
full rather than "int".
Best regards,
--
Michel Alexandre Salim
identities:
https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2
1 month, 3 weeks