Note:
Reorder dependencies and remove luasec and luasocket because
they are no longer required.

We need to build new reForis package and its language files

Right now, reForis is a little bit ahead and has different versions of
dependencies and if you have a full build, there are issues that
static files are not present in reforis package and languages packages
does not have forisjs.mo.

If you dont have forisjs.mo, you end up with not working reForis.
It crashes with:

AttributeError: 'NullTranslations' object has no attribute 'json_catalog'
      args = ("'NullTranslations' object has no attribute 'json_catalog'",)
      with_traceback = <built-in method with_traceback of AttributeError object>

However, if you build locally reforis and copy those packages on the
router, it works flawlessly.

The issue right now is that reforis and reforis-shield are using the
same shared package languages and they could be different. We decided to remove
translations from reForis Shield. There was also possibility to
have separate language files for reForis, but it should not be
necessary.

Alter API calls after splitting of storage and nextcloud

initial release as standalone module

Split nextcloud and storage

After doing this update, it is required to reboot your router.
Because then it couldn't find anything at IP/nextcloud.
And once you do restart, it guides you to update it, and since then
it works flawlessly.

Nobody is even sure that smrt works with latest versions of Turris OS.
We are not even sure if anyone is even using it. Only few pieces were
send out. At the moment there is also no one in team with knowledge
about smrt and its firmware.

it should handle forwarding foris-controller messages
between mqtt message buses

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

Also drop PKG_RELEASE back to 1. Fix packages are intended to be
installed and immediatelly removed so there is no reason to bump version
on release as package should not be installed in system to upgrade it.

This plugin is for uCollect that is no longer avaliable. This package
should not be available at all now in system.

For some reason this fixes usage of liburiparser in HBD. It probably
relies on prefix variable tampering or something and because
liburiparser was inserting full paths instead of composing them from
prefix it created issue of mixed includes.

In Turris OS 3.x there was UCI config and integration for sshd. Now
there is just standard config. Simple fix is to move original generated
one to appropriate location.

This move only happens if configuration of sshd in UCI is not the
default one. The second check is if target file exists and that is just
to make sure but it should always be there.

Thanks to David Hopfmueller for pointing this out.

The reason for append is to not overrule rules configured in Luci.

There can potentially be some drop rule as well and that was one of the
original reasons why insert was used instead of append but until such
case is discovered this should be enough.

This checks and reorders sentinel-firewall config on firewall start.
This is not ideal as this reorder is not applied in firewall run when
reorder happens and there seems to be no reliable way to request
firewall reload from firewall script itself (would cause firewall
nesting with unknown results).

We also does not have to reorder in uci-defaults as new config sections
are always appended so they are the last one, making that operation
useless code.

This removes any preserved rules from firewall. Firewall3 removes any
rules in chains and tables it manages but others ignores. This is
considered as feature (as some lists survive reload) but for our use
case it is not ideal as scripts just insert rules in appropriate
location. Instead removing all rules we previously added and were
preserved is better option in this case.

There is one exception and those are our rules that are terminations for
chains created by us. We are not removing those chains and so we do not
want to remove those  rules as well. We prevent that by using slightly
different comment. We do not add additional commentary and drop colon.
Because of missing colon this rule is not matched and is not removed.
For termination rule additional comment about source is not necessary so
we are not loosing anything.

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

After some debuging found out that CONFIG_CC_OPTIMIZE_FOR_SIZE breaks
Omnia kernel and while at it added extra kernel options for LEDs.

With introduction of link signatures for packages updater can now detect
changes in link dependencies and reinstall package without relying on
package bumps. Thanks to that we no longer have to reinstall all
packages when switching between unsafe branches as link signature is
going to change and updater is going to reinstall affected packages
without need to reinstall all packages.

This also allows easy to simulate update between no just stable branches
but also between unstable ones (usable for testing of updates to future
major or minor release).

There was invalid commit command in uci-default script. This changes it
to correct one.

This also adds prerm script to remove UCI section from config. It should
not stay in place when package is removed.