We dont think that it is necessary anymore as we have a workaround for
such case. More details in commit 7ca8dc88
("Revert "Revert "patches/openwrt: reload network on wpad update""")

We experienced this issue with recent update in OpenWrt 19.07 main
repository, when hostapd was updated due to vulnerability in P2P group
information and after update Wi-Fi was not working anymore and it was
required to do reboot of the router, but /etc/init.d/network restart
does its job as well.

This reverts commit e46d84a6.

Throw away PKG_RELEASE bump. We need to have same version in HBS for
now, which is there PKG_RELEASE=5

Throw away PKG_RELEASE downgrade as we are patching hostapd anyway in
another patch, so we dont need it.

We want to push Turris OS 5.1.9 as soon as possible and this commit is
issue for us as after updating all packages then Wi-Fi networks are down
and they came back only while doing reboot.

We will take a look at it further, this is quick&dirty solution.

Backport of upstreamed solution https://github.com/openwrt/packages/pull/14202

This is new-old service that feeds entropy from atsha.

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

Commit aeaf3437 ("patches/openwrt: make some SFP modules work ...")
backported some patches from upstream kernel, but the backport missed
move of 3 lines of code. Fix this.

Fixes: aeaf3437 ("patches/openwrt: make some SFP modules work ...")

Marek Behun authored 4 years ago and Josef Schlehofer committed 4 years ago

This backports commits a006dbf06e5df and 7a77233ec6d11 from upstream
kernel to make some SFP modules with non-conformant EEPROM information
work.

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

This patch should have been clearly in openwrt repository not in
packages feed.
Everything seems to work even without it so I think that we can drop
it safely. I am not even sure if it applies two year after its creation.

Josef Schlehofer authored 4 years ago and Jan Pavlinec committed 4 years ago

We have our own package turris-webapps-transmission, so we don't need to
patch transmission package.

Josef Schlehofer authored 4 years ago and Jan Pavlinec committed 4 years ago

In this pull commit, I backported hwinfo which will help us to provide system information, monitor hardware information and diagnostics.
hwinfo is already in packages repository, but it will be part of OpenWrt
21.xx release.

This resets uboot environment. We of course do not want to do it and
even if so we do not plan to do it right now or possibly this way.

These packages are necessary for running Gitlab CI on Omnia/Mox.
This should help knot-resolver team to test kresd on
different architectures.

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

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.

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

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).

In preparation for new reboot fix testing remove these hacks. They do
not work anyway.