Compiling libuuid was failing with the following error:

```c
libuuid/src/gen_uuid.c: In function 'uuid_generate_time_generic':
libuuid/src/gen_uuid.c:536:33: error: initializer element is not constant
  THREAD_LOCAL int  cache_size = cs_min;
```

The error was previously detected, and a fix was provided in
52abdf6a , where the GCC minimum version
was increased to 8 (GCC version 8 supports using const-declared
variables as constant expressions in some cases).

Unfortunately, the solution did not work as the `min_version` field of
the `[gcc]` section was being overwritten by its value in
`component/defaults.cfg`.
This is because `util-linux` (where libuuid config is located) is a
transient dependence of `defaults.cfg` through `python3`.

Fortunately, the error is already [patched upstream](https://github.com/util-linux/util-linux/commit/07e5c29d501c19e7af84fecb5915e0f9f94cb49f)
in version 2.40.1, so we can just upgrade the library to the latest
version instead, which we do here.

See merge request nexedi/slapos!1609

patch for arbitrary code execution due to heap corruption in `git_index_add`

see: https://github.com/libgit2/libgit2/security/advisories/GHSA-j2v7-4f6v-gpg8
https://security-tracker.debian.org/tracker/CVE-2024-24577

Commit de5e381d broke build of
MariaDB >= 10.5. There were warnings about that with 10.4.

Since openssl 3.0, Config.pm is lauched with shebang "/usr/bin/env perl"
so perl from slapos must be in the PATH.

This is not backward compatible: you'll need to either fix your DB
or disable explicitly.

See !1601

See merge request !1558

git >= 2.31 crash on fetch-pack when running gitlab-backup

see: https://lore.kernel.org/git/20240606133605.602276-1-kirr@nexedi.com/T/#m9d454aadc8857b84f17d1a331739f7399cf1bbf8

See merge request nexedi/slapos!1592

Assert `open62541` library works by joining a multicast group.

Update component to be suitable for osie-coupler

1.0.0 was not python2 compatible, setuptools ignored this

See merge request nexedi/slapos!1257

This brings updates of many dependencies on python3, while mostly
keeping the same versions for python2.

This enables a new `erp5-py3` test in software/slapos-sr-testing, which
should pass already, but with NEO and WCFS being marked as expected
failure or skipped for now.

This also brings pylint support on python3, which we will be able to
reuse in software/slapos-testing.
Co-authored-by: Kazuhiko SHIOZAKI <kazuhiko@nexedi.com>
Co-authored-by: Arnaud Fontaine <arnaud.fontaine@nexedi.com>
Co-authored-by: Bryton Lacquement <bryton.lacquement@nexedi.com>

This bring new versions of jupyter, numpy and other scientific python
software. This impacts software/jupyter, which will now run more recent
versions and prepares stack/erp5 for python3 support, while not
impacting the python2 version.

This reverts commit 6c399134.

This is not really specific to python2, it is specific to ERP5, now that
ERP5 uses python3, the naming became not really good

This reverts 1b291415 (component/ghostscript: Workaround for slaprunner
paths with double slashs, 2021-06-02) and 4e9a9cf1 (component/tesseract:
Workaround for slaprunner paths with double slashs, 2021-08-19). We no
longer support slappruner and these commits were causing issues on
python3