Because commit subject is too long, I'd need to choose word accepted
even though it was applied (I mean cherry-picked) by OpenWrt developers
to OpenWrt 19.07. So, we don't need to have it in backports anymore.

In OpenWrt 19.07 packages feed, there was updated zerotier from master
branch to version 1.6.2 and it includes same workaround

In OpenWrt 19.07 packages feed, there was updated zerotier from master
branch and it includes same workaround

dhparam package was removed so it is not longer available for install.
Instead turris-cagen dhparam generation should be used.

Karel Koci authored 4 years ago and Karel Koci committed 4 years ago

This triggers removal of uboot environment configuration from system so
we can set there correct one by installing new version of uboot-tools.

In case of Turris Mox we have to do also additional trickery as file we
want to generate is part of mox-support package originally. With this
update it is dropped but we have to let it be removed fist before we
recreate it by installing new version of uboot-tools otherwise updater
would remove that file as part of mox-support package cleanup phase.

Karel Koci authored 4 years ago and Karel Koci committed 4 years ago

Packge Mox-support was providing uboot environment configuration file
but more appropriate is to use OpenWrt approach with generated
configuration.

This should move Mox little bit closer to upstream.

By replacing Repository with provided one user can generate package
lists pointing to repo.turris.cz. That means it uses packages from there
but lists are local one. Of course user can replace hbs with any other
branch name and such.
The primary point there is to specify public keys.

Co-authored-by: Karel Kočí <cynerd@email.cz>
Co-authored-by: Vojtech Myslivec <vojtech.myslivec@nic.cz>

This is just stylistic change. It removes dirname and instead relies on
string operation. There should be no way of having in $0 anything else
other than some valid path. That is last part has to be at least
/name_of_file. This means that we do not have to rely on dirname and we
can safely just remove anything after last slash (including that slash).
We user dirname only for paths in sub-directories.

This fixes bug that caused force-make to go to fallback immediately
after first batch of retries.

As a benefit it also adds some reporting of what is going on. This
should help to locate fail point as well as to inform about execution
progress.

Note:
This should extend amount of supported ath9k mPCIe cards.
It was disabled because of module size.

OpenWrt does it in different way, but it is included in OpenWrt 19.07.

This fixes updater error:
[string "base-conditional.lua"]:6: '=' expected near 'Install'

Merge of luci-lighttpd and patch that was providing webapps files for
luci to package turris-webapps-luci caused file collision. The cause is
that patch adding webapps did not change version of luci-base package.
The solution is to just reinstall luci-base package to remove
conflicting files.
This affects mostly only HBL and HBD. It is most probable that update
between versions is going to bump LuCI version and solve it that way
insteand. At the same time it won't harm to have this.

This is replaced by dedicated package turris-webapps-luci.

This also eats up separate package luci-lighttpd. Configuration for
lighttpd is now provided by turris-webapps-luci (in a compatible way to
webapps).

There are multiple changes to updater's lists. In most cases it is about
moving packages around and grouping them together to simplify future
maintenance.

Significant change is usage of conditional requests. Updater now
installs Foris plugins not because some package list was selected but
because some package was installed. This makes it so users running
minimal setup (without web interface) can use package lists and still
have full system with it.

One important change to note here is that SSH client was moved from
minimal base list to terminal-apps. The reason is that it is not
essentially required for router's functionality or access. It is more
about secondary usage from CLI so it should have been part of
terminal-apps all time along.

This has to be string otherwise it won't do replan. In the end it is not
that of a big issue. Subsequent execution later on removes this fix
package.

This has to be string otherwise it won't do replan. In the end it is not
that of a big issue. Subsequent execution later on removes this fix
package.

Co-authored-by: Jan Pavlinec <jan.pavlinec@nic.cz>
Co-authored-by: Vojtech Myslivec <vojtech.myslivec@nic.cz>