Paul Moore
Paul Moore
Here is the release-2.5/v2.5.x branch backport: https://github.com/seccomp/libseccomp/pull/439
With the backport PR now posted, I'm closing this PR, thanks again everyone!
I'm not aware of anyone working on this, are you interested? It's possible that the work going on in the thread below may have an impact on this: * https://lore.kernel.org/audit/[email protected]/
As a reminder @rwk141414, we do not provide individual Linux distribution support here, especially for enterprise distributions with their own established support mechanisms. We're obviously very happy to hear about...
Done @rprobaina and thanks! (related, I'll take a closer look at the GH perms to see if I can fix that, although last I checked they were too coarse)
Good catch @rprobaina, thanks :) I don't really keep a history of the changes, contributors to this file as I keep it as a single patch to make rebasing easier...
Fixed, thanks for the help!
Considering that Python v2 is long past it's EOL date, I'm wondering how much of an issue this is in practice, and would moving from "python" to "python3" end up...
> For example on Ubuntu/Debian, `python` requires another package: https://packages.debian.org/sid/python-is-python3. It seems to be distro dependent. On my Arch system it appears the "python" package supplies both `python` and `python3`...
> Anyway, this looks fine to me and seems to be in keeping with the official Python guidance. > > ``` > Acked-by: Paul Moore > ``` Ooops, one more...