Re: ansible triggers a syscall error in python on -current

2023-12-17 Thread Ganymede
I can confirm ansible works again after the last packages update. Thanks, problem solved. Le 16/12/2023 à 02:01, Stuart Henderson a écrit : You'll need packages built against the new libc version, a snapshot should be available fairly soon. (Specifically in this case it's for py3-cryptpgraphy,

Re: ansible triggers a syscall error in python on -current

2023-12-15 Thread Stuart Henderson
You'll need packages built against the new libc version, a snapshot should be available fairly soon. (Specifically in this case it's for py3-cryptpgraphy, but you'll need a rebuilt version of rust to be able to build that). On 2023/12/15 22:52, Ganymede wrote: > Hi, > > It seems that on

ansible triggers a syscall error in python on -current

2023-12-15 Thread Ganymede
Hi, It seems that on -current, ansible triggers a syscall error in python3.10, at least on amd64. No problem on -stable. I don't understand what's going on, but I could reproduce the bug simply by running: $ ansible --help msyscall 9d7972ed000 a8000 error Segmentation fault (core dumped)