... Kernel is appended a + to the version string when there are locally
modified files - which we have. This is prevented by the existence of the
.scmversion file.
This reverts commit 8b520c63ac705aa2c35579ebfbc053b5b6a1bccb.
CI tests also use parallel ATA interfaces in QAEmu - we probably should keep it
for "poor" virtualisation.
Note: Intel does not provide a compatible QAT version. There is a custom patch
which make QAT compile for the specified Kernel version. This patch will change
the source to a non backwards-compatible version - this is fine as we run 5.8
anyways.
The logic of generating the required firmware file name has been moved from
build-linux-firmware.sh directly into list-required-firmware.py which makes
much more sense. That move was made by Daniil Baturin - I only did the
integration part. Thanks!
Because of FRR bug 6062 (https://github.com/FRRouting/frr/issues/6062) frr-reload in frr 7.3.0 and 7.3.1
needs to be patched to work properly. without this patch frr-reload will allways compare against
a blank/empty running configuration.
During the build of conntrack-tools we need to first install the recent version
of libnetfilter-conntrack-dev build in a previous step as its a dependency.
Instead of writing the same code over and over again, place the common parts
into a Jenkins Library which is then consumed by every individual build Job.
This not only makes it less complex, but also increases maintainability by
several magnitudes.
Instead of scattering build instructions accross individual repositories for
some additional packages we want to build from latest Debian releases, this
is a proof-of-concept how to integrate an individual package Pipeline into the
overall VyOS build repository.
A dedicated Jenkins job will be required for this Pipeline but it will only
compile if files are actually changes in the directory path relevant for
this components.
All registered Git submodules were out of date. Even worse some of the modules
are no longer in use and have been replaced by upstream packages.
Keeping invalid information is even worse then no information. All required
VyOS packages can be found in the future build-packages script.
