Back out use of pledge(2) in mupen64plus-ui-console.
Although pledge(2) was only called at the last possible moment, after
nearly all initialization had been done, it turns out there was one case
I missed: if the user is playing with a ujoy(4) gamepad, then SDL will
call ioctl(2) with USB_GET_REPORT_DESC. No pledge(2) promise allows this.
Due to mupen64plus's design, pledge(2) cannot be moved any later. The
USB initialization takes place in a .so plugin with a documented public
API. Calling pledge(2) inside the plugin would certainly break other
mupen64plus frontends.
It may be possible to reintroduce pledge(2) in mupen64plus, by hoisting
joystick initialization to a place that gets executed earlier. However,
this too might not be possible without breaking other frontends.
Other alternatives could be to modify SDL's joystick initialization to
not require USB_GET_REPORT_DESC, or perhaps to add a new "ujoy" promise.
Either of these would benefit other SDL/ujoy(4)/pledge-using programs
[13 lines not shown]
rpki-client: only accept BGPsec certs with a single AS number
We've long been pointing out that the possibility of adding multiple AS
numbers and in particular AS ranges to BGPsec Router Certificates is at
best dubious. Enforce that there is a single AS, encoded as an ASID, not
as an ASRange with a single element (cf. eid7653 to RFC 3779).
Prompted by a report by Xie Yifan
with/ok claudio job
update to lapack-3.12.1, various patches backported from upstream (mostly
concerning lines becoming too long for a punch card after macro changes,
it seems)
rpki-client: check purpose for .cer files in Manifests
Only intermediate CAs and BGPsec certificates are allowed in a Manifest
fileList. Check this is the case, otherwise stop processing the cert.
Missing check reported by Xie Yifan
ok claudio job
import ports/textproc/py-pyjson5, sparc64 tests/ok tb@
JSON5 serializer and parser library for Python 3 written in Cython.
The serializer returns ASCII data that can safely be used in an HTML
template. Apostrophes, ampersands, greater-than, and less-then signs are
encoded as unicode escaped sequences.
Unless the input contains infinite or NaN values, the result will be
valid JSON data.
The parser can handle all valid JSON5 1.0.0 and JSON data can be read,
unless the nesting level is absurdly high.
regress/xstate: Dynamic xstate buffer size
The current implementation leads to an "xstate buffer too small" error
on newer machines with an xstate area bigger than 1KiB. Allocate the
buffer dynamically from PT_GETXSTATE_INFO kernel info.
ok anton@
Remember last pane or type of location for double and triple clicks and
correctly handle it changes between first and second or second and
third. GitHub issue 4795 from Shaobo Song.
lang/go module: use TEST_TARGET as default target for MODGO_TEST_TARGET instead of ALL_TARGET
default to ALL_TARGET (keep previous value)
while here, pass TEST_ENV in MODGO_TEST_CMD
ok tb@
Update to numpy 2.4.1, help/ok sthen, no objection daniel
Tested in bulks on amd64 by me and on i386 by sthen.
Tested on aarch64, amd64, i386 and sparc64.
jca will address riscv64 brekage in tree.
Update to prusaslicer 2.9.3, tested/ok ian (a long time ago)
From Renato Aguiar (maintainer)
Pull in Gentoo's fixes for newer Boost, so this compiles with 1.88
and hopefully also with 1.89.
remove lacp support from trunk(4)
lacp is better supported by aggr(4). users of lacp in trunk(4)
should migrate to aggr(4).
trunk(4) and the lacp support inside it is one of the last chunks
of code that still requires the netlock in the ethernet stack. the
last time i tried to fix this i ended up writing aggr(4), and nothing
about this code has improved since then. the other protos such as
failover and loadbalance are trivial in comparison and will be easy
to improve in the future.
discussed with and no objections from many
