Turris OS packages issueshttps://gitlab.nic.cz/turris/os/packages/-/issues2023-08-16T14:35:25+02:00https://gitlab.nic.cz/turris/os/packages/-/issues/913Add ethtool dependency for turris-diagnostics2023-08-16T14:35:25+02:00Martin MatějekAdd ethtool dependency for turris-diagnostics## Description
In case SFP module is plugged into the SFP slot, then turris-diagnostics fails to fetch info about SFP, due to missing `ethtool`.
`turris-diagnostics` requires `ethtool` for its network module. See: https://gitlab.nic.cz...## Description
In case SFP module is plugged into the SFP slot, then turris-diagnostics fails to fetch info about SFP, due to missing `ethtool`.
`turris-diagnostics` requires `ethtool` for its network module. See: https://gitlab.nic.cz/turris/diagnostics/-/blob/master/modules/40_network.module#L58-62
## How to reproduce
On Turris OS 6.2.4, Turris Omnia, clean install from medkit. Turris SFP module is plugged in the SFP slot.
Run the network diagnostics
```sh
$ turris-diagnostics network
```
## Expected behavior
At least some output from ethtool should appear.
```
$ turris-diagnostics network
############## network
[...]
== SFP (eth2) ==
Identifier : 0x03 (SFP)
Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID)
Connector : 0x22 (RJ45)
[...]
************** network
```
## Actual behavior
`ethtool` is not found and we don't get any info about SFP.
```
$ turris-diagnostics network
############## network
[...]
== SFP (eth2) ==
modules/module.sh: line 61: ethtool: not found
************** network
```
## Proposed solution
Add `ethtool` dependency for `turris-diagnostics` and include `ethtool` in base TOS image/medkit.https://gitlab.nic.cz/turris/os/packages/-/issues/910fix: oneshot rename `br-guest_turris` -> `br-guest-turris` in /etc/config/net...2023-08-16T14:35:26+02:00Martin Matějekfix: oneshot rename `br-guest_turris` -> `br-guest-turris` in /etc/config/network on TOS 6.xPrepare oneshot fix package that will rename `br-guest_turris` -> `br-guest-turris` in existing configuration.
Currently there can be two different, but valid, configurations for guest network bridge - for details, see turris/foris-cont...Prepare oneshot fix package that will rename `br-guest_turris` -> `br-guest-turris` in existing configuration.
Currently there can be two different, but valid, configurations for guest network bridge - for details, see turris/foris-controller/foris-controller#256.
Essentially, either configs should work fine, but it is confusing to have two possible valid configuration when debugging something in turris diagnostics. It would be nice to have just one supported configuration.
This will align existing network config after migration from TOS 5.x to 6.x with the value, that foris-controller expects.Turris OS 6.3.0https://gitlab.nic.cz/turris/os/packages/-/issues/871resolver-conf: DNS spoofing via DHCP2023-08-16T14:35:32+02:00rwapplerresolver-conf: DNS spoofing via DHCPFix available here as part of https://github.com/CZ-NIC/turris-os-packages/pull/65 (rather long Pull request)
The patch in question is here: https://github.com/CZ-NIC/turris-os-packages/pull/65/commits/8e3963287b998215e5aa09cc477a0aede4...Fix available here as part of https://github.com/CZ-NIC/turris-os-packages/pull/65 (rather long Pull request)
The patch in question is here: https://github.com/CZ-NIC/turris-os-packages/pull/65/commits/8e3963287b998215e5aa09cc477a0aede44a84c4
----
# Details
Due to the way `/etc/resolver/dhcp_host_domain_ng.py` is called, a DHCP client not providing a hostname will spoof the DNS by creating an additional DNS record with the same name as the router.
1. `dhcp_host_domain_ng.py` reads the host name to add a lease for from the environment variable `HOSTNAME`. On UNIX-like systems, this is a well known environment variable, usually set to the hostname of the actual system. When the DHCP client does not provide a hostname, it is not overwritten or unset.
2. A new A-record is created with the name of the router, but a different IP
3. router potentially unreachable
It could also be considered an issue in interface design.2022-11-20https://gitlab.nic.cz/turris/os/packages/-/issues/854lighttpd run it under its own user2023-08-16T14:35:34+02:00Josef Schlehoferlighttpd run it under its own user1. Our Lighttpd package runs under root
- Related: https://gitlab.nic.cz/turris/os/packages/-/commit/f699fff40ce2e9c2607ad4f1536268d3135472ae + https://forum.turris.cz/t/shield-s-hbk-nefunguje-reforis/17711 (you need to start lighttpd ...1. Our Lighttpd package runs under root
- Related: https://gitlab.nic.cz/turris/os/packages/-/commit/f699fff40ce2e9c2607ad4f1536268d3135472ae + https://forum.turris.cz/t/shield-s-hbk-nefunguje-reforis/17711 (you need to start lighttpd manually = ``lighttpd -D -f /etc/lighttpd/lighttpd.conf``)
2. OpenWrt package runs under http/www-data
- User and group its created by its init script, which I find odd. It should be done by Makefile.
- [ ] Switch to upstream solution
- [ ] Drop lighttpd from our feedTurris OS 6.2.0Filip HronFilip Hronhttps://gitlab.nic.cz/turris/os/packages/-/issues/848Nextcloud - forbidden2023-08-16T14:35:36+02:00Josef SchlehoferNextcloud - forbiddenIn Turris OS 6.0, Nextcloud does not work as it shows "403 Forbidden". This was tested in new Nextcloud installations, but it should affect the existing ones.In Turris OS 6.0, Nextcloud does not work as it shows "403 Forbidden". This was tested in new Nextcloud installations, but it should affect the existing ones.Turris OS 6.0https://gitlab.nic.cz/turris/os/packages/-/issues/844treewide: switch to AUTORELEASE2023-08-16T14:35:37+02:00Josef Schlehofertreewide: switch to AUTORELEASEWe should switch to the [AUTORELEASE variable](https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=9ae3c6f94c616cfbf854d3ec749c7fafc9893942) instead of manually increasing PKG_RELEASE. This avoids cases, where it was forgotten.We should switch to the [AUTORELEASE variable](https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=9ae3c6f94c616cfbf854d3ec749c7fafc9893942) instead of manually increasing PKG_RELEASE. This avoids cases, where it was forgotten.Turris OS 6.0https://gitlab.nic.cz/turris/os/packages/-/issues/835ouidb: fix "OUT DB file doesn't exists"2023-08-16T14:35:39+02:00Martin Matějekouidb: fix "OUT DB file doesn't exists"Fix `oui.db` file location so it could be actually utilized for MAC vendor lookup.
See original script:
https://gitlab.nic.cz/turris/ouidb/-/blob/master/ouidb#L19
and more recent version:
https://gitlab.nic.cz/turris/os/packages/-/bl...Fix `oui.db` file location so it could be actually utilized for MAC vendor lookup.
See original script:
https://gitlab.nic.cz/turris/ouidb/-/blob/master/ouidb#L19
and more recent version:
https://gitlab.nic.cz/turris/os/packages/-/blob/develop/utils/ouidb/files/ouidb#L19https://gitlab.nic.cz/turris/os/packages/-/issues/818Turris-auth release 0.3.02023-08-16T14:35:41+02:00Karel KociTurris-auth release 0.3.0Fixes:
* [x] turris/turris-auth#9Fixes:
* [x] turris/turris-auth#9Turris OS 6.0https://gitlab.nic.cz/turris/os/packages/-/issues/803No $EDITOR set in environment2023-08-16T14:35:43+02:00Jan BetikNo $EDITOR set in environmentThere is no $EDITOR set in environment; some tools refuse to work.
```
root@turr1x:~# echo $EDITOR && crontab -e
/bin/sh: /usr/bin/vi: not found
crontab: "/usr/bin/vi" exited with status 127
```
I would prefer to set the `EDITOR /usr/b...There is no $EDITOR set in environment; some tools refuse to work.
```
root@turr1x:~# echo $EDITOR && crontab -e
/bin/sh: /usr/bin/vi: not found
crontab: "/usr/bin/vi" exited with status 127
```
I would prefer to set the `EDITOR /usr/bin/vim` in global .bashrc file located at `/etc/bash.bashrc`Turris OS 5.3.1https://gitlab.nic.cz/turris/os/packages/-/issues/787tos3to4 : migration don't finish (omnia)2023-08-16T14:35:44+02:00Ghost Usertos3to4 : migration don't finish (omnia)turris_version : 3.11.23
[updater-log.tar.xz](/uploads/a136c5c9326e2c11b4839a30d3ac40cd/updater-log.tar.xz)
I tried to do the migration, but here the output of notifications:
```
Error from 2021/08/04 12:59:40
Updater approvals were dea...turris_version : 3.11.23
[updater-log.tar.xz](/uploads/a136c5c9326e2c11b4839a30d3ac40cd/updater-log.tar.xz)
I tried to do the migration, but here the output of notifications:
```
Error from 2021/08/04 12:59:40
Updater approvals were deactivated to prevent problems during migration to the latest major release of Turris OS!
×
Update from 2021/08/04 12:59:58
• Installed version 1.0.3-1 of package tos3to4
×
Error from 2021/08/04 13:02:06
Updater selhal:
[string "transaction"]:327: [string "transaction"]:151: Collisions:
• /etc/crontabs/.keep: cronie (new-file), vixie-cron (existing-file)
• /usr/bin/crontab: cronie (new-file), vixie-cron (existing-file)
• /usr/bin/updater-supervisor: updater-supervisor (new-file), updater-ng-supervisor (existing-file)
• /etc/updater/hook_postupdate/99_approvals_cleanup: updater-supervisor (new-file), updater-ng-supervisor (existing-file)
• /etc/cron.d/.keep: cronie (new-file), vixie-cron (existing-file)
• /etc/cron.d/updater: updater-supervisor (new-file), updater-ng-supervisor (existing-file)
• /usr/share/updater/l10n_supported: l10n_supported (existing-file), l10n-supported (new-file)
• /etc/init.d/cron: cronie (new-file), vixie-cron (existing-file)
×
Update from 2021/08/04 13:02:06
• Installed version 7.5.0-2 of package libgcc
• Installed version 1.1.24-2 of package libc
• Installed version 0.12.1-3.1 of package libjson-c
• Installed version 2020-05-25-66195aee-1 of package libubox
• Installed version 2018-02-04-c7e938d6-1 of package jsonfilter
• Installed version 1.30.1-8 of package busybox
• Installed version 20200601-1 of package ca-certificates
• Installed version 1.1.1k-1 of package libopenssl
• Installed version 2.2.9-1 of package libexpat
• Installed version 1.0.8-1 of package libbz2
• Installed version 1.1.24-2 of package libpthread
• Installed version 5.2.5-1 of package liblzma
• Installed version 1.2.11-3 of package zlib
• Installed version 3.4.2-1 of package libarchive
• Installed version 0.9.4-2 of package liburiparser
[updater-log.txt](/uploads/2fd885d07a31a6034c05bd83e1791c1f/updater-log.txt)• Installed version 20200601-1 of package ca-bundle
• Installed version 7.66.0-3 of package libcurl
• Installed version 2.1.11-1 of package libevent2
• Installed version 5.1.5-3 of package liblua
• Installed version 2019-09-01-415f9e48-4 of package libuci
• Installed version 2019-09-01-415f9e48-4 of package libuci-lua
• Installed version 69.1.3-1 of package updater-ng
• Installed version 5.1.5-3 of package lua
• Installed version 3.0-rc1-20130909-5 of package luasocket
• Installed version 0.9.54-1 of package json4lua
• Installed version 1.6.3-1 of package pkglists
• Installed version 7.66.0-3 of package curl
• Installed version 2020-06-17-51e16ebf-1 of package libuclient
• Installed version 2020-06-17-51e16ebf-1 of package uclient-fetch
• Installed version 2021-01-31-c5dccea9-1 of package opkg
• Installed version 8.30-2 of package coreutils
• Installed version 8.30-2 of package coreutils-sort
• Installed version 2019-09-01-415f9e48-4 of package uci
• Installed version 2.6.0-3 of package switch-branch
• Installed version 2.2.1-3 of package tos3to4-early
• Installed version 1-1 of package fix-pkglists-options
• Installed version 1-1 of package fix-pkglists-hardening-options
×
Error from 2021/08/04 13:52:59
Updater selhal:
[string "transaction"]:327: [string "transaction"]:151: Collisions:
• /etc/crontabs/.keep: cronie (new-file), vixie-cron (existing-file)
• /usr/bin/crontab: cronie (new-file), vixie-cron (existing-file)
• /usr/bin/updater-supervisor: updater-supervisor (new-file), updater-ng-supervisor (existing-file)
• /etc/updater/hook_postupdate/99_approvals_cleanup: updater-supervisor (new-file), updater-ng-supervisor (existing-file)
• /etc/cron.d/.keep: cronie (new-file), vixie-cron (existing-file)
• /etc/cron.d/updater: updater-supervisor (new-file), updater-ng-supervisor (existing-file)
• /usr/share/updater/l10n_supported: l10n_supported (existing-file), l10n-supported (new-file)
• /etc/init.d/cron: cronie (new-file), vixie-cron (existing-file)
```
Since, I can't acces to the router with ssh.
Seems that I'm now in the middle of the migration, but it don't finish.Turris OS 5.2.5 (formal release)https://gitlab.nic.cz/turris/os/packages/-/issues/771updater-ng: version 69.1.32023-08-16T14:35:46+02:00Karel Kociupdater-ng: version 69.1.3With improved error message.
* turris/updater/updater!289With improved error message.
* turris/updater/updater!289Turris OS 5.2.3https://gitlab.nic.cz/turris/os/packages/-/issues/770foris-storage-plugin: fix version 3.0.12023-08-16T14:35:47+02:00Martin Matějekforis-storage-plugin: fix version 3.0.1Fix setup of nextcloud accountFix setup of nextcloud accountTurris OS 5.2.3https://gitlab.nic.cz/turris/os/packages/-/issues/762nextcloud: cronjob breaks nextcloud configuration2023-08-16T14:35:49+02:00Martin Matějeknextcloud: cronjob breaks nextcloud configuration## Description
`cron.php` included with nextcloud gets executed periodically. If there is no configuration (e.g. after instalation) it somehow fails with following output and creates empty `config.php`.
HBS (5.1.10)
```
May 5 20:40:01...## Description
`cron.php` included with nextcloud gets executed periodically. If there is no configuration (e.g. after instalation) it somehow fails with following output and creates empty `config.php`.
HBS (5.1.10)
```
May 5 20:40:01 turris crond[24321]: (nobody) CMD (/usr/bin/php-cli -f /srv/www/nextcloud/cron.php)
May 5 20:40:01 turris crond[24319]: (nobody) CMDOUT (PHP Warning: fileperms(): stat failed for /srv/www/nextcloud/data/nextcloud.log in /srv/www/nextcloud/lib/private/Log/File.php on line 83)
May 5 20:40:01 turris crond[24319]: (nobody) CMDOUT ({"reqId":"2LX5Nd3mNTNs08DNy0G1","level":3,"time":"2021-05-05T20:40:01+00:00","remoteAddr":"","user":"--","app":"PHP","method":"","url":"--","message":"fileperms(): stat failed for /srv/www/nextcloud/data/nextcloud.log at /srv/www/nextcloud/lib/private/Log/File.php#83","userAgent":"--","version":""})
May 5 20:40:01 turris crond[24319]: (nobody) CMDOUT ({"reqId":"2LX5Nd3mNTNs08DNy0G1","level":3,"time":"2021-05-05T20:40:01+00:00","remoteAddr":"","user":"--","app":"cron","method":"","url":"--","message":{"Exception":"Exception","Message":"Not installed","Code":0,"Trace":[{"file":"/srv/www/nextcloud/lib/base.php","line":651,"function":"checkInstalled","class":"OC","type":"::","args":[]},{"file":"/srv/www/nextcloud/lib/base.php","line":1089,"function":"init","class":"OC","type":"::","args":[]},{"file":"/srv/www/nextcloud/cron.php","line":42,"args":["/srv/www/nextcloud/lib/base.php"],"function":"require_once"}],"File":"/srv/www/nextcloud/lib/base.php","Line":282,"CustomMessage":"--"},"userAgent":"--","version":""})
May 5 20:40:01 turris crond[24319]: (nobody) CMDOUT (PHP Warning: fileperms(): stat failed for /srv/www/nextcloud/data/nextcloud.log in /srv/www/nextcloud/lib/private/Log/File.php on line 83)
May 5 20:40:01 turris crond[24319]: (nobody) CMDOUT ({"reqId":"2LX5Nd3mNTNs08DNy0G1","level":3,"time":"2021-05-05T20:40:01+00:00","remoteAddr":"","user":"--","app":"PHP","method":"","url":"--","message":"fileperms(): stat failed for /srv/www/nextcloud/data/nextcloud.log at /srv/www/nextcloud/lib/private/Log/File.php#83","userAgent":"--","version":""})
May 5 20:40:01 turris crond[24319]: (nobody) CMDOUT ({"reqId":"2LX5Nd3mNTNs08DNy0G1","level":3,"time":"2021-05-05T20:40:01+00:00","remoteAddr":"","user":"--","app":"PHP","method":"","url":"--","message":"chmod(): No such file or directory at /srv/www/nextcloud/lib/private/Log/File.php#84","userAgent":"--","version":""})
```
HBT (5.2.0)
```
May 5 21:15:01 turris crond[25474]: (nobody) CMD (/usr/bin/php-cli -f /srv/www/nextcloud/cron.php)
May 5 21:15:02 turris crond[25472]: (nobody) CMDOUT ({"reqId":"W0nzxPKvqhxjJgLWjROt","level":3,"time":"2021-05-05T21:15:02+00:00","remoteAddr":"","user":"--","app":"cron","method":"","url":"--","message":{"Exception":"Exception","Message":"Not installed","Code":0,"Trace":[{"file":"/srv/www/nextcloud/lib/base.php","line":654,"function":"checkInstalled","class":"OC","type":"::","args":[]},{"file":"/srv/www/nextcloud/lib/base.php","line":1095,"function":"init","class":"OC","type":"::","args":[]},{"file":"/srv/www/nextcloud/cron.php","line":42,"args":["/srv/www/nextcloud/lib/base.php"],"function":"require_once"}],"File":"/srv/www/nextcloud/lib/base.php","Line":282,"CustomMessage":"--"},"userAgent":"--","version":""})
```
## Expected behaviour
No `config.php` should exist and user should be able to configure nextcloud from Foris.
## Actual behaviour
Empty `config.php` is created as side effect, thus from foris point of view it looks like nextcloud is already configured.
In order to be able to configure nextcloud from Foris, it is necessary to remove `/srv/www/nextcloud/config/config.php`.Turris OS 5.2.0Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/761install foris-controller-nextcloud-module with nextcloud2023-08-16T14:35:50+02:00Martin Matějekinstall foris-controller-nextcloud-module with nextcloudUp to the version 0.4.2, `foris-controller-storage-module` included both storage and nextcloud, but nextcloud was cut out into it's own module [foris-controller-nextcloud-module](turris/os/packages!529).
AFAIK the `foris-controller-next...Up to the version 0.4.2, `foris-controller-storage-module` included both storage and nextcloud, but nextcloud was cut out into it's own module [foris-controller-nextcloud-module](turris/os/packages!529).
AFAIK the `foris-controller-nextcloud-module` is not installed alongside `nextcloud` on TOS 5.2.0 when user selects `NAS` + `Nextcloud` package list.
Which means that there is no user friendly way to setup nextcloud, unless user somehow manage to install `foris-controller-nextcloud-module` package.
cc: @jschlehoferTurris OS 5.2.0Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/753foris-controller-storage-module: release 0.8.12023-08-16T14:35:52+02:00Martin Matějekforis-controller-storage-module: release 0.8.1* [x] [Milestone foris-controller-storage-module: RAID improvements](https://gitlab.nic.cz/turris/foris-controller/foris-controller-storage-module/-/milestones/1)* [x] [Milestone foris-controller-storage-module: RAID improvements](https://gitlab.nic.cz/turris/foris-controller/foris-controller-storage-module/-/milestones/1)Turris OS 5.2.0https://gitlab.nic.cz/turris/os/packages/-/issues/752prerm : sentinel i agree with eula: syntax error - unexpected EoF2023-08-16T14:35:54+02:00Josef Schlehoferprerm : sentinel i agree with eula: syntax error - unexpected EoFMOX HBK:
```
ERROR:Failed operations:
sentinel-i_agree_with_eula/prerm: /usr/lib/opkg/info//sentinel-i_agree_with_eula.prerm: /usr/lib/opkg/info/sentinel-i_agree_with_eula.prerm-pkg: line 10: syntax error: unexpected end of file (expect...MOX HBK:
```
ERROR:Failed operations:
sentinel-i_agree_with_eula/prerm: /usr/lib/opkg/info//sentinel-i_agree_with_eula.prerm: /usr/lib/opkg/info/sentinel-i_agree_with_eula.prerm-pkg: line 10: syntax error: unexpected end of file (expecting "fi")
```Turris OS 5.2.0https://gitlab.nic.cz/turris/os/packages/-/issues/747foris-controller-sentinel-module: sentinel-state-indication2023-08-16T14:36:22+02:00Martin Matějekforis-controller-sentinel-module: sentinel-state-indication* [x] [foris-controller-sentinel-module: sentinel state indication](https://gitlab.nic.cz/groups/turris/foris-controller/-/milestones/5)* [x] [foris-controller-sentinel-module: sentinel state indication](https://gitlab.nic.cz/groups/turris/foris-controller/-/milestones/5)Turris OS 5.3.0https://gitlab.nic.cz/turris/os/packages/-/issues/735localrepo is broken2023-08-16T14:36:24+02:00Josef Schlehoferlocalrepo is brokenI tried to install package which was locally compiled in Turris OS 6.0, and I can not do it:
```
root@turris:~# opkg install knot-resolver_5.3.0-1_aarch64_cortex-a53.ipk
Package knot-resolver (5.2.1-2) installed in root is up to date.
/...I tried to install package which was locally compiled in Turris OS 6.0, and I can not do it:
```
root@turris:~# opkg install knot-resolver_5.3.0-1_aarch64_cortex-a53.ipk
Package knot-resolver (5.2.1-2) installed in root is up to date.
/usr/bin/opkg-pkgupdate-wrapper.sh: line 130: localrepo: not found
```
Localrepo is not found. See:
```
root@turris:~# opkg list-installed | grep localrepo
localrepo - 0.2.1-2
root@turris:~# opkg files localrepo
Package localrepo (0.2.1-2) is installed on root and has the following files:
/usr/bin/localrepo
/etc/updater/conf.d/localrepo.lua
root@turris:~# /usr/bin/localrepo
-ash: /usr/bin/localrepo: not found
```Turris OS 6.0https://gitlab.nic.cz/turris/os/packages/-/issues/726turrishw: Support for Turris 1.x2023-08-16T14:36:26+02:00Martin Matějekturrishw: Support for Turris 1.x- [x] turris/turrishw%"TurrisHW - Turris 1.x support"- [x] turris/turrishw%"TurrisHW - Turris 1.x support"Turris OS 5.2.2https://gitlab.nic.cz/turris/os/packages/-/issues/722turris-survey: release v0.42023-08-16T14:36:28+02:00Vojtech Myslivecturris-survey: release v0.4Release initial version of Turris-Survey
related:
- [x] turris/sentinel/turris-survey#4 (turris/sentinel/turris-survey!6)Release initial version of Turris-Survey
related:
- [x] turris/sentinel/turris-survey#4 (turris/sentinel/turris-survey!6)Turris OS 5.3.4