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.

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

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

It is now in specific packages in Turris OS packages

My fault... :(

To be able to proxy netdata through lighttpd and to require some sort
of authetification, changing the defaults to forbid remote access from
every IPv4 private segment possible by default (security enhancement)
and disabling compression (to make proxy work).

This is requirement for webapps integration.

Makefile was modified in upstream. This is just simple rebase of
existing patch.

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

Upstream reworked provides for wget packages. Now this parch is no
longer required because no package now provide itself.

Included in upstream

Remove the part with PKG_RELEASE bump, so I dont need to rebase it
every time, when I bump syslog-ng in upstream

We provide now our own version of luajit package with moonjit. We can
later think about upstreaming it.

My patch, which was present in the hack folder, is no longer applying as
mariadb was updated in OpenWrt 18.06, 19.07 and master branches.
This patch was meant to be a workaround as something in OpenWrt was
changed and it caused inconsistency in the installation of packages and we
would like to have provided mariadb in our feed, this was the easiest
and a quicker solution at that time.

Solution is provided in this commit: a42ef21a740653ee76146bfccee1ab6afbd65539