Turris OS packages issueshttps://gitlab.nic.cz/turris/os/packages/-/issues2023-08-16T14:36:31+02:00https://gitlab.nic.cz/turris/os/packages/-/issues/697tos3to4: migration of network adds interfaces to invalid networks2023-08-16T14:36:31+02:00Karel Kocitos3to4: migration of network adds interfaces to invalid networksScript `switch_and_vlans` migrates switch and it seems to add interfaces to any interface but that includes VPNs.. that is wrong.
(Originally reported in turris/turris-os-packages#696).Script `switch_and_vlans` migrates switch and it seems to add interfaces to any interface but that includes VPNs.. that is wrong.
(Originally reported in turris/turris-os-packages#696).Turris OS 5.1.5https://gitlab.nic.cz/turris/os/packages/-/issues/696wireguard: DEVICE_CLAIM_FAILED after TOS 3->5 upgrade2021-01-10T13:21:40+01:00David Hopfmuellerwireguard: DEVICE_CLAIM_FAILED after TOS 3->5 upgradeAfter upgrading from TOS 3.11.19.1 to 5.1.3 wireguard fails to load and LuCI displays an `Unknown error (DEVICE_CLAIM_FAILED)`. This seems to be caused by an `option ifname 'something'` entry in wireguard's `config interface` section. Re...After upgrading from TOS 3.11.19.1 to 5.1.3 wireguard fails to load and LuCI displays an `Unknown error (DEVICE_CLAIM_FAILED)`. This seems to be caused by an `option ifname 'something'` entry in wireguard's `config interface` section. Removing the offending option solves the issue.Turris OS 5.1.5https://gitlab.nic.cz/turris/os/packages/-/issues/678Migration from 3.x: postupdate hooks are for some reason skipped when migrating2020-12-08T22:39:17+01:00Karel KociMigration from 3.x: postupdate hooks are for some reason skipped when migratingFor some reason postupdate hooks in updater are probably skipped. There are already two reported instances when this happened.
One report is that kernel version wasn't updated on Turris 1.x.
Second report is that alternatives were not ...For some reason postupdate hooks in updater are probably skipped. There are already two reported instances when this happened.
One report is that kernel version wasn't updated on Turris 1.x.
Second report is that alternatives were not updated.
Both issues can be solved by running appropriate postupdate hook.Turris OS 5.2.0https://gitlab.nic.cz/turris/os/packages/-/issues/544Migrate settings of samba 3 to samba 4 (at least some minimal subset)2020-02-24T15:42:45+01:00Karel KociMigrate settings of samba 3 to samba 4 (at least some minimal subset)With Turris OS 5.0 there is switch from Samba version 3 to version 4. Those have incompatible configuration.
We should migrate configuration somehow because we are initializing switch.With Turris OS 5.0 there is switch from Samba version 3 to version 4. Those have incompatible configuration.
We should migrate configuration somehow because we are initializing switch.Turris OS 5.0