Branch :
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
| 3f059e80 | 2026-08-11 12:42:41 | drop @pkgpath/@conflict markers previously used for updates from 7.0/7.1 | ||
| 1b8729cc | 2026-01-24 23:37:14 | update to py3-pcapy-1.1.0 | ||
| 14491920 | 2025-11-03 11:46:49 | update py-pcapy to pcapy-ng-1.0.9, switching to the fork which unbreaks runtime with python 3.10 and build with 3.13. tested with "queryparse" from dnsperf which now works (failed before) and pbgpp (failed before, still fails). | ||
| cf45b401 | 2025-04-29 10:39:05 | sync PLISTs for setuptools ports | ||
| a4770540 | 2024-12-21 11:38:32 | handle py3.12 switchover in net | ||
| 41b34e25 | 2024-05-06 12:23:44 | bump REVISION for py3.10 -> py3.11 switch | ||
| e6dba44e | 2022-11-13 19:37:40 | use MODPY_PYBUILD for most of net/ | ||
| dae9f91e | 2022-11-13 15:28:39 | bump for MODPY_DEFAULT_VERSION_3 change | ||
| b1d3b852 | 2022-08-15 22:34:52 | py-pcapy: remove a hack in setup.py that hasn't been needed for years and breaks with newer setuptools. the repo that this port currently uses has seen no activity for a while; patch is taken from the fork "pcapy-ng". this should move across to pcapy-ng anyway because this old one will fail with Python 3.10; not doing that now as various deps will need adjusting for paths | ||
| 3f5796b9 | 2022-03-11 19:45:43 | drop RCS Ids |