We have two services that indicate boot finish. Those are
start-indicator and rainbow. They have start level 99 but these services
have it set as well and thus sometimes start after indicator. The result
is that tests relying on indicator can initially fail because they just
start too early.
It is also a good idea to just not keep 99 level for use like
start-indicator so this moves all services to earlier level rather than
just affected ones.

The dependency on create_notification includes gettext-tools that
conflicts with gettext and prevents continuation of migration.

There is probably not other solution than just removing this dependency.
We can't use trick with virtual package as we are using old updater at
that moment that considers it as error.

Glenn Strauss authored 3 years ago and Michal Vasilek committed 3 years ago

* add a patch to fix fix use-after-free bug in mod_alias
* refresh patches
* remove an upstreamed meson-zstd patch

* refresh patches
* remove disabling kres_gen_test - this was disabled because it broke
  cross compilation in 5.4.0, but is now fixed.

this bug resulted in crontab -e failing when $EDITOR was not set because
the configure script detected vi path from the host system which is
probably /usr/bin/vi, but OpenWrt has vi in /bin/vi

Compile and run tested on Turris 1.1, powerpc8540

Remove PKG_MAINTAINER line as this package is in our repository and thus
we maintain it. Also, this version was not in OpenWrt. There is a newer
version for OpenWrt 21.02+

it's needed when running nextcloud_install:

    + sudo -u nobody php-cli ./occ maintenance:install ...
    An unhandled exception has been thrown:
    Error: Call to undefined function OC\filter_var() in /srv/www/nextcloud/lib/private/Setup.php:479

Fixes: da729192 ("foris-controller:
update to version 3.0.0")

In the past the tos3to4-early was installed alongside of updater but
that wasn't ideal so it was moved to be installed later with latest
version of updater after the first replan. This created issue that
script that should allow newest updater to run wasn't installed and
executed. At the same time we do not want to install tos3to4-early due
to its dependencies that we can't simply overcome in the old updater.
The alternative is to simply introduce tos3to4-earliest that contains
the simple localrepo removal script. This is going to be dependency of
updater and thus installed before the new version is installed.

Added:
- wan: qos limit on traffic

Changed:
- web: `list_languages` now uses reForis translations instead of Foris translations to determine available localization,
    since Foris is no longer present in TOS 5.3.0
- time: timezone is now set by backend based on provided region and city

Fixed:
- networks: fix reading multiple interfaces of wan (e.g. bridge)
- wan: ipv6_address in 6in4 may contain prefix as well

Note: foris-controller now requires `turris-timezone`

* add lighttpd-mod-auth to dependencies of lighttpd-mod-authn_*
* uncomment module import in lighttpd-mod-auth

fixes netdata and pakon being accessible without password because Basic
auth didn't work

Nor-update is provided by package turris-nor-update, which installs
nor-update into /usr/sbin

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

Latest changes in PaKon makes it separate web app independent of Foris.

The original check was that master can be pushed only with develop
branch. It is what we mostly want but there are cases when we do not
update develop and only master that are valid as well. The example of
such operation is merge of develop to master, which is always
fast-forward due to our workflow.

This halts push only if master commit is not ancestor of develop instead
of halting it always when develop is not being updated.

* dependencies will be automatically loaded when the module is
  installed, so we don't need to explicitly import them in lighttpd
  config files
* add missing dependencies to packages, this worked because on a normal
  TOS system, other packages with the required dependencies are
  installed, but could potentially break when the dependencies change
* remove lighttpd-mod-authn_file dependency since it's not used anywhere
* remove lighttpd-mod-auth dependency when the package already depends
  on lighttpd-mod-auth_pam

This makes backup scripts more accessible and also adds additional
features. The short list is:
* Inclusion of sysupgrade files (OpenWrt's way to mark files for backup)
* Optional inclusion of modified configuration files
* More strict inclusion for previously included files
* Protection against recovery from other major versions of OS

The last change is the most important as it is not just plain addition
but the incompatible change. This is intentional as the protection is
more desirable than the compatibility. The use of the scripts is same as
the previously but recovery of backup from different major OS version is
not allowed.

This reverts commit 14abc044.

This reverts Foris part as well. The reForis part was reverted in
33ab8eff.
It turns out that my assumption that both Foris and reForis behave the
same that lead to only partial revert was invalid and Foris as it seems
it all right. This matches the behavior of reForis.

The second patch is fix. This backports patch that fixes issues with
scripts terminating but not correctly closing all outputs results into
hang.

The first patch is a feature. The turris-build repository contains
second part of it and it is already merged. It is not desirable to
release new version of updater because of other changes thus backporting
only this patch is a good solution.

Similarly to ebc12ecdb66a9261ba3d5cd06e87588764ac53aea2c64bd4c226f13cc2bf77d4

The `--` there was originally intended to disable processing of options
and thus protect against situation where password starts with dash. It
turns out that python processes arguments in such a way that anything
after command specification is automatically considered as argument and
not as option for python interpreter.

This also sets it to explicitly call Python3 compared to python as that
might call Python 2 that is not in package's dependencies and thus the
code might break if it would be called with it.