Bundle spatch in container to apply patches locally

[daskol]

Private clouds often lack direct Internet access. If the spatch binary is missing and Spatch-as-a-Service is unavailable, drbd-module-loader cannot patch the DRBD sources and build drbd.ko.

This pull request adds a step to the Dockerfiles to install spatch (provided by the coccinelle package). The coccinelle package is available on Debian-based distributions and on AlmaLinux 8 via EPEL 8.

[WanzenBug]

Looks sensible. What about the other RHEL-clone versions (9 and 10)?

Note that not all of those coccinelle versions will actually work with DRBD, as it needs some rather new version for some patches. But it should still fall back to the old version in that case, so that should be fine.

[daskol]

Unfortunately, coccinelle is missing in AlmaLinux 9 and 10, i.e. EPEL 9 and 10 (see pkgs.org for list of distros which provides coccinelle). Also, spatch version does not satisfy minimal version requirements >=1.1.1 according to DBRD's kernel module compatibility page. Thus, I've reverted the latest commit.

Also, Debian Bullseyes does not satisfy the spatch version requirements as well. I decided to keep it for consistency (all Debian containers has spatch) and vague terms (i.e. "but 1.1 is not good enough") leave a chance that this spatch version will work.

Distro	spatch	OCaml
almalinux8	1.0.7	4.07.0
almalinux9	N/A	N/A
almalinux10	N/A	N/A
bookworm	1.1.1	4.13.1
bullseye	1.1.0	4.11.1
jammy	1.1.1	4.13.1
noble	1.1.1	4.14.1
trixie	1.3.0	5.3.0

I also considered an option to use binary distribution for coccinelle without Python bindings (see the downloads page). However, it is dynamically linked against glibc 2.38 (August 2023). Thus, it will definitely will not work for all distribution except for trixie.

PS The issue #30 seems to be related.

[daskol]

Just a kind reminder.

[WanzenBug]

Thanks!