until I figure out whether it's possible to set up slapd there by
analogy with what the scapy action on GitHub does.
It's a follow-up to https://github.com/secdev/scapy/pull/4539.
openssl got updated on Fedora Rawhide and its defaults are no longer
compatible with the test suite. `.config/ci/openssl.py` sets it up and
gets the tests to pass there.
Closes https://github.com/secdev/scapy/issues/4470
by dropping the tox-current-env kludge. The idea was to bypass
virtual environments created by tox and use the system packages
directly. It's no longer needed because tox itself isn't run anywhere
any more on Packit and UTscapy is used instead.
This PR:
- enables manual_trigger in packit
I do think that it's overkill for every PR to be checked against all of Fedora's plateforms. Packit should probably, at least for now, only be triggered manually when the PRs are related to components that might break on unorthodox plateforms.
The script takes the Fedora package, edits the spec file to make it
compatible with the upstream test suite and then it's all run on all
those architectures on the latest stable Fedora release and Fedora
Rawhide. (Rawhide is kind of a testing relase but it's useful in terms of
catching things like https://github.com/secdev/scapy/issues/4280
reproducible with relatively new packages only).
It was originally prompted by
https://github.com/secdev/scapy/issues/3847 (where the Debian
autopkgtest was run on big-endian and 32-bit machines) and should
hopefully make it easier to catch various issues before they land.
It has been tested since the beginning of 2023 so it should be stable at
this point.
Evgeny Vereshchagin