Architectures like amd64, i386,... are reported by
`dpkg --print-architecture`, though we can't rely on those
since we don't have only Debian based systems.
So switch to the actual output, as provided by `uname -m`.
Don't list options alphabetically though, as x86_64 AKA amd64
should be the most common option, and "other" makes sense to
present as last option.
Change-Id: I2d8a39d9807f0134665d25de6d89c22a4141a4f9
The rtpengine GitHub issue tracker is not a support forum,
so let's point user to the mailing list instead, and provide
initial bug report + feature request templates, while at it.
Change-Id: I7414b94131def5f19cdc5cc17d41684007b12bf2
bookworm is the current Debian stable release as of 2023-06-10,
so switch from bullseye to bookworm.
Change-Id: I7df785862dd6a1466d426c147dce5877e66ec9d3
So far we used ubuntu-latest for the unit-tests, though this is no
longer using Ubuntu/focal (wich we used to build for) but Ubuntu/jammy
(22.04 LTS, AKA Jammy Jellyfish) nowadays.
Instead let's stick to ubuntu-22.04 since we also use a specific release
for the packaging part.
FTR: see https://github.com/actions/runner-images for the overview
of available GitHub Actions Runner Images
Change-Id: I41f2fe1c35bccb40f1f8df59b23446ab27ce1033
Instead of having to rely on external repositories (like the
ubuntu-cloud-archive/yoga-staging PPA for the debhelper v13 backport),
let's use the pkg script instead. The pkg scripts ensure that the
debian/ directory looks as expected for the according distribution. So
for executing coverity + unit-tests in the Ubuntu/focal / ubuntu-20.04
environment on GitHub, let's use pkg/deb/backports/focal for generating
the according Debian source tree.
Related change in pkg: make `wrap-and-sort` execution optional. We don't
have devscripts installed by default in Ubuntu/focal / ubuntu-20.04
environment on GitHub, while usage of wrap-and-sort can be considered
optional for our purposes.
Change-Id: Ic252b323408fab557e3f151a93f61aa8fac1a30f
ubuntu-20.04 + ubuntu-latest (currently also pointing at 20.04) don't
provide debhelper v13 (required for debhelper-compat (= 13)), therefore
our workflow fails with:
| The following packages have unmet dependencies:
| builddeps:. : Depends: debhelper-compat (= 13)
| E: Unable to correct problems, you have held broken packages.
So enable the ubuntu-cloud-archive/yoga-staging PPA,
which provides a backport of debhelper v13:
https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/yoga-staging/+packages
and fixes our failing unity + coverity builds on github.
While at it, using apt-get with `-qq` displays only the following
message on package installation problems:
| E: Unable to correct problems, you have held broken packages.
Whereas with `-q`, we get the actual underlying problem, being:
| The following packages have unmet dependencies:
| builddeps:. : Depends: debhelper-compat (= 13)
| E: Unable to correct problems, you have held broken packages.
Change-Id: I67439a8f2f27e902710af43ff52599c8a58a5f98
In commit a4ee01d27f we switched to debhelper compat level 13.
debhelper v13 isn't available in (plain) Debian buster,
and therefore the Debian pipeline for buster fails with:
| The following packages have unmet dependencies:
| builddeps:. : Depends: debhelper-compat (= 13)
Since we updated packaging for bullseye, also adapt the GitHub
actions / workflow accordingly.
Change-Id: I411a6ab16ee48c5c5fc1ca43c58c016df83e1ff7
Recent builds fail with
Run sudo apt-get build-dep -qq -y -Ppkg.ngcp-rtpengine.nobcg729 .
E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/pool/main/s/systemd/libsystemd-dev_245.4-4ubuntu3.6_amd64.deb 404 Not Found [IP: 52.154.174.208 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
E: Failed to process build dependencies
Change-Id: If7d4d0be41bbc93b7e131fd1e68094a9a374a6f2
UBSAN doesn't print stack traces by default. Enable them.
The GLib slice allocator must be disabled for proper leak checks and
must be instructed to always use malloc instead.
Change-Id: Ic4fe5ad38aa4460fbe43858b97226cce7d658038
To get better backtraces we should build with -ggdb and -O0. And to
avoid gcc's ASAN implementation erroring out due to libasan not being
passed first as part of LD_PRELOAD, we disable the check via
ASAN_OPTIONS.
Change-Id: I6e8c422fef3c8fdcdc20e815292ffca4f6d6becb
We need to pass these on through environment otherwise we are overriding
the whole build flags.
Change-Id: I3fd856af2624f84afe73427dfb359e8bfc3acaa8
Fixes: commit f791bf03f9
The Ubuntu release used does not have the required package, so we need
to disable it via our build-profile.
Change-Id: I7b929bf5b8cfc60a75e72cbd3b92036cb28d4066
Fixes: commit f791bf03f9
Rename the workflow, as this is only in charge of running the shellcheck
tests. Having a workflow per checker also makes them more modular, and
easier to reuse in other projects by simply copying the files around.
And makes it easier to see what checks are currently available from
the filenames.
Rename the job to "test", for correctness, as it has implicit ordering
and meaning within the GitHub action built-in stages.
Change-Id: I3987fc03111d94a8bc64e9103e43cb4d05925e12
The file utils/build_deps.sh was removed in commit e580c7c7f8,
adjust shellcheck execution accordingly.
Change-Id: Ibe454e98d02e026ef5cade9401e73a04975e6cc3
Orgad Shaneh
Richard Fuchs
Michael Prokop
Guillem Jover