In this file there were two packages:
cshark - which is being compiled just fine in OpenWrt 18.06
libpsl - it was added after branch-off of OpenWrt 19.07, so we are
disabling something which does not exist

upstream

Those packages shouldn't be broken anymore according to
https://downloads.openwrt.org/releases/packages-18.06/powerpc_8540/packages/
they are being compiled in upstream. There are some packages which can be handy for us like mariadb.

Karel Koci authored 5 years ago and Karel Koci committed 5 years ago

OPKG seems to be using uclient-fetch if wget is not available but once
wget command is on system it uses it. The problem is that we have URLs
with SSL and so we need wget with SSL support but in default updater
minimalizes amount of installed packages so it chooses wget-nossl
variant over full wget.

In Linux 4.13, a new kernel option was introduced to allow userspace
access to RTC NVMEM. This option is off by default, making the NVMEM
inaccessable. Since there is at least one application utilizing it, this
patch adds `/sys/class/rtc/rtc0/device/nvram` back.

Signed-off-by: Ondřej Caletka <ondrej@caletka.cz>
(cherry-picked from commit e09c946d)

Fixes turris/turris-build#87

This removes files that were providing pkglists redirection for updater
versions in 4.0-alpha* releases.

First officially forward compatible version is 4.0-beta1 and that does
not have any pkglists in medkit while still expecting these lists in old
location. The advantage is that in medkit those lists are not enabled so
update is possible and nobody should still run 4.0-beta1 now so we can
drop this without a problem.

Now release tags have a correct date and include all release notes for that
particular release.

This reverts commit 1bd0f379.

This was created to migrate Turris OS 4.0-alpha* releases. The first
supported version 4.0-beta1 already contains correct path with board
specific path so there is no need to preserve these obsolete ones.
Non the less they are also wrong with additional introduced changes.
They point to pkglists in invalid location.

This requires also removal of code on build server to not use --obsolete
option and to not deploy those.

This patch caused a regression on Mox Peridot-Topaz configuration.
This is a temporary solution.

Signed-off-by: Marek Behún <marek.behun@nic.cz>

This adds support for applying patches only for a specific board.
This should be a temporary solution for a regression on Mox (patch for
Omnia multi CPU DSA broke Mox Peridot-Topaz configuration).

Signed-off-by: Marek Behún <marek.behun@nic.cz>