This bug was fixed in the package python-trio - 0.24.0-1ubuntu1
---
python-trio (0.24.0-1ubuntu1) noble; urgency=medium
* d/patches: In test_socket.py, handle PermissionError
which may be thrown if setsockopt() is invoked
with SO_BINDTODEVICE (LP: #2054772)
-- Pushkar Kulk
** Changed in: python-trio (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054772
Title:
python-trio 0.24.0-1 FTBFS on noble
To manage notifications abou
Checked with the Launchpad team if I could get access to a builder VM so
that we can investigate this failure, but they hinted on the negative
side.
I might try to run the build in a noble LXD-container (on a VM), like LP
does. But, I have submitted a patch that disables the failing call from
the
I am not 100% sure if this call, failing with a PermissionError,
requires root privileges:
sock.setsockopt(tsocket.SOL_SOCKET, tsocket.SO_BINDTODEVICE, None, 0)
I tried to write small tests in Python and C, as a non-root user, but
cannot trigger a PermissionError (Python) or a system-call failur
** Merge proposal linked:
https://code.launchpad.net/~pushkarnk/ubuntu/+source/python-trio/+git/python-trio/+merge/461337
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054772
Title:
python-trio
