https://github.com/openwrt/openwrt/commit/32621086c3b0c641609580bdf83d4c731caa7f5e
added some patches that only apply to OpenWrt 21.02's linux 5.10, this commit
rebases those patches for linux 5.15

Debian package `libyaml-dev` is required on build host to successfully build package `kernel/linux`.

Otherwise we will get following errors:

mltree.o -L/build/staging_dir/target-aarch64_cortex-a53_musl/usr/lib -lyaml
/usr/bin/ld: skipping incompatible /build/staging_dir/target-aarch64_cortex-a53_musl/usr/lib/libyaml.so when searching for -lyaml
/usr/bin/ld: skipping incompatible /build/staging_dir/target-aarch64_cortex-a53_musl/usr/lib/libyaml.a when searching for -lyaml
/usr/bin/ld: cannot find -lyaml
/usr/bin/ld: skipping incompatible /build/staging_dir/target-aarch64_cortex-a53_musl/usr/lib/libyaml.so when searching for -lyaml
collect2: error: ld returned 1 exit status
time: package/kernel/linux/compile#2.05#0.33#2.39
    ERROR: package/kernel/linux failed to build.

Fixes a kernel panic

The error message says that $DEFAULT_UPDATER_VERSION will be used, but
it wasn't actually set anywhere which resulted in an unbound variable
error.

I accidentally pushed an older version of the commit without feedback
addressed, this commit addresses the feedback in
!619

Nextcloud needs mysqld

(cherry picked from commit af6587e7)

Michal Hrusecky authored 2 years ago and Michal Vasilek committed 2 years ago

We don't care that much about binary sizes. What we care much more about
is performance.

These optimizations are not available for Turris 1.x

Example from openssl benchmark on Turris Omnia:

-blowfish cbc     31828.77k    34072.13k    34575.86k    34862.61k    34960.07k    34880.97k
+blowfish cbc     44087.01k    48574.86k    50495.69k    50045.71k    50657.71k    50395.53k

-aes-256 cbc      34569.29k    36977.21k    38553.42k    38331.73k    38312.02k    38460.17k
+aes-256 cbc      37079.18k    40329.57k    41345.76k    41927.39k    41947.61k    41910.39k

Start syncthing when installed. This makes sure that when the app is
installed through reforis, it will be available and working without any
manual configuration.

Enable syncthing in /etc/config by default to make sure when we
enable the service, syncthing can run without having to manually
enable it in the config.

Users, by default, expect that the service will run automatically and that
they will configure it while the service is running to see what was changed
and what is the behavior of each function there. This change is going to enable
syncthing to run after installing it instead of tweaking the config manually
(in LuCI or by hand). This is somehow different than how OpenWrt does it. They
force users to configure the app before running. Once they are confident that
the configuration looks good, they enable it, which is also good behavior.
Still, we need to improve the user experience and somehow make it different as
we want that even non-IT guys/girls can configure what they need and install
what they need in our simplified interface called (re)Foris, where we provided
list of packages, which they can ...

Start transmission when the package is installed. This makes sure that when
the app is installed through reforis, it will be available and working without
any manual configuration.

Enable transmission in /etc/config by default to make sure when we
enable the service, transmission can run without having to manually
enable it in the config.

Users, by default, expect that the service will run automatically and that
they will configure it while the service is running to see what was changed
and what is the behavior of each function there. This change is going to enable
transmission to run after installing it instead of tweaking the config manually
(in LuCI or by hand). This is somehow different than how OpenWrt does it. They
force users to configure the app before running. Once they are confident that
the configuration looks good, they enable it, which is also good behavior.
Still, we need to improve the user experience and somehow make it different as
we want that even non-IT guys/girls can configure what they need and install
what they need in our simplified interface called (re)Foris, where we provided
list of packages, which they can install and if it does not run by default, it
looks like something is wrong. For transmission, we also provide
Transmission WebApp, the integration for Turris OS, which you can find on the
landing page and easily click on it and start configuring it.

This patch comes from pending pull request to OpenWrt master branch:
https://github.com/openwrt/openwrt/commit/bf8a89084bebbc18670c27098d45fa6406b27e9f

missed in 53670fa1

Let's distinguish the version between HBK/HBT/HBS branches, otherwise,
it is same if it is not different and makes it harder for users to
know which branch or even the version they are using on the router.

This helps and also, it is good to mention that BIND was updated,
because it fixes three CVEs since I backported it to
OpenWrt 22.03 and OpenWrt 21.02.

This is WIP as I want to look at it further, because I want to look if
we can copy all the files in bin instead specifying all binaries by
hand, which would prevent this issue.

There are also other updates like unbound, kernel, but lets include only
highlights for this release.

Removed patches were included in Linux kernel