updater issueshttps://gitlab.nic.cz/turris/updater/updater/-/issues2019-05-06T17:47:30+02:00https://gitlab.nic.cz/turris/updater/updater/-/issues/104Postponed updates2019-05-06T17:47:30+02:00Ghost UserPostponed updatesSupport a mode where the updater runs, emails what it wants to do and then it either waits for certain amount of time or waits for a user to confirm the actions.Support a mode where the updater runs, emails what it wants to do and then it either waits for certain amount of time or waits for a user to confirm the actions.https://gitlab.nic.cz/turris/updater/updater/-/issues/103Restricted security level2020-11-12T02:24:11+01:00Ghost UserRestricted security levelWhile we accept the `Restricted` security level of a sandbox, it acts the same as `Remote`.
* [x] Implement the URI matching and reject the ones that don't match.
* [x] Guess the pattern from the script location.While we accept the `Restricted` security level of a sandbox, it acts the same as `Remote`.
* [x] Implement the URI matching and reject the ones that don't match.
* [x] Guess the pattern from the script location.https://gitlab.nic.cz/turris/updater/updater/-/issues/102Make signature checking work2020-11-12T02:24:15+01:00Ghost UserMake signature checking workThe code to check signatures (URL.sig) was implemented some time ago, but it hasn't been checked until now. Fix it so it works in normal circumstances. Also, make the final setup:
- [x] Check signatures of repositories
- [x] Check signa...The code to check signatures (URL.sig) was implemented some time ago, but it hasn't been checked until now. Fix it so it works in normal circumstances. Also, make the final setup:
- [x] Check signatures of repositories
- [x] Check signatures of scripts
- [x] Enable checking in the default config scripts
- [x] Set up the testing & deploy keys
- [x] Create a package for the testing key, make sure it is *not* installed by defaulthttps://gitlab.nic.cz/turris/updater/updater/-/issues/100Deploy updater-ng on all omnia routers2020-11-12T02:24:14+01:00Ghost UserDeploy updater-ng on all omnia routers2016-06-30https://gitlab.nic.cz/turris/updater/updater/-/issues/99Re-structure URLs of the updater-ng configs2020-11-12T02:24:15+01:00Ghost UserRe-structure URLs of the updater-ng configsWe want to be able to provide different configs not only by a branch, but according to turris-version or serie. The user-lists need to be per-branch as well.
Change them on the server and in the default updater-ng script as well.We want to be able to provide different configs not only by a branch, but according to turris-version or serie. The user-lists need to be per-branch as well.
Change them on the server and in the default updater-ng script as well.https://gitlab.nic.cz/turris/updater/updater/-/issues/94Handle data.tar.xz2019-05-06T17:47:27+02:00Ghost UserHandle data.tar.xzHandle the possibility of the package content to be inside data.tar.xz instead of data.tar.gz. This is what debian now does and there's a slight chance someone might want to do so in openwrt. On the other hand, consider the xz dependency.Handle the possibility of the package content to be inside data.tar.xz instead of data.tar.gz. This is what debian now does and there's a slight chance someone might want to do so in openwrt. On the other hand, consider the xz dependency.https://gitlab.nic.cz/turris/updater/updater/-/issues/93Read only state variables2020-11-12T02:24:13+01:00Ghost UserRead only state variablesProvide the variables:
- serial
- model
- board_name
- turris_version
- installedProvide the variables:
- serial
- model
- board_name
- turris_version
- installedhttps://gitlab.nic.cz/turris/updater/updater/-/issues/92Flags support2020-11-12T02:24:12+01:00Ghost UserFlags supportProvide the `flags` variable (actually, a clever table) and the `StoreFlags` command.Provide the `flags` variable (actually, a clever table) and the `StoreFlags` command.https://gitlab.nic.cz/turris/updater/updater/-/issues/91Complex deps descriptions2020-11-12T02:24:12+01:00Ghost UserComplex deps descriptionsProvide parser for more complex dependencies between packages. However, it is not required to have full support of handling them ‒ `And()` is simple, but we may just pick the first from `Or()` and we can ignore `Not()` for now. This is t...Provide parser for more complex dependencies between packages. However, it is not required to have full support of handling them ‒ `And()` is simple, but we may just pick the first from `Or()` and we can ignore `Not()` for now. This is to be able to parse future scripts in some limited manner.https://gitlab.nic.cz/turris/updater/updater/-/issues/90Forward-compatibility of language2020-11-12T02:24:14+01:00Ghost UserForward-compatibility of languageGo through the language design document and decide what needs to be supported or at least mocked for forward compatibility. This means, we want to have the language support at such a level future scripts won't cause syntax errors and wil...Go through the language design document and decide what needs to be supported or at least mocked for forward compatibility. This means, we want to have the language support at such a level future scripts won't cause syntax errors and will allow the current updater to update itself.https://gitlab.nic.cz/turris/updater/updater/-/issues/89Download definicions of the user-lists2020-11-12T02:24:14+01:00Ghost UserDownload definicions of the user-listsGet the userlist definitions and place them wherever the old updater did, so we preserve the behavior and foris still offers them.Get the userlist definitions and place them wherever the old updater did, so we preserve the behavior and foris still offers them.https://gitlab.nic.cz/turris/updater/updater/-/issues/88Auto-generator of the configurations2019-05-06T17:47:13+02:00Ghost UserAuto-generator of the configurationsThere are certains parts of the updater-ng configurations that should be auto-generated (for example a list of core packages is better taken from a compiled root). Also, signing the configurations is needed.
- [x] Generate all the userl...There are certains parts of the updater-ng configurations that should be auto-generated (for example a list of core packages is better taken from a compiled root). Also, signing the configurations is needed.
- [x] Generate all the userlists
- [x] What about the `compile_turris_fix` script?
- [ ] Specification of packages through a regular expression/wildcard (eg. `luci-app-*` or `kmod-*`).
- [x] Enable it for the good old blue turris.
- [x] Get rid of strange extra packages, like `openssh_server_nuci_support`.Michal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/updater/updater/-/issues/87Updater auto-run resilience2020-11-12T02:24:11+01:00Ghost UserUpdater auto-run resilienceFew things need to be done to call the automatic running of the updater production-ready. This includes:
- [x] Porting the unstuck mechanism.
- [x] Timeouts for calling of notifiers and stuff
- [x] Run from cron at a random time (twice ...Few things need to be done to call the automatic running of the updater production-ready. This includes:
- [x] Porting the unstuck mechanism.
- [x] Timeouts for calling of notifiers and stuff
- [x] Run from cron at a random time (twice a day)https://gitlab.nic.cz/turris/updater/updater/-/issues/86Accept unknown extra parameters2020-11-12T02:24:15+01:00Ghost UserAccept unknown extra parametersWe want to be forward compatible and ignore parameters we don't know. That way we would be able to at least parse the scripts, upgrade updater itself and then run again.
But at least provide warnings, so athors of scripts can spot typos.We want to be forward compatible and ignore parameters we don't know. That way we would be able to at least parse the scripts, upgrade updater itself and then run again.
But at least provide warnings, so athors of scripts can spot typos.https://gitlab.nic.cz/turris/updater/updater/-/issues/79Steal config files of uninstalled packages2019-05-06T17:47:12+02:00Ghost UserSteal config files of uninstalled packagesWhen a package is installed that claims a config file owned (and left behind) by an `not-installed` package, remove the config file from the status of the `not-installed` package. And if there are no more configs in there, wipe it.When a package is installed that claims a config file owned (and left behind) by an `not-installed` package, remove the config file from the status of the `not-installed` package. And if there are no more configs in there, wipe it.https://gitlab.nic.cz/turris/updater/updater/-/issues/77Nuci support2020-11-12T02:24:15+01:00Ghost UserNuci supportCreate and update at least some basic set of status files during the updater run, so the nuci plugin provides useful information.Create and update at least some basic set of status files during the updater run, so the nuci plugin provides useful information.https://gitlab.nic.cz/turris/updater/updater/-/issues/76Allow scripts and packages to be missing2020-11-12T02:24:14+01:00Ghost UserAllow scripts and packages to be missingIt is allowed for a repository to not exist (if explicitly allowed in its extra options). Allow similar option for the `Install` and `Script` commands. This'll allow constructing more generic lists (like user-lists) which will work acros...It is allowed for a repository to not exist (if explicitly allowed in its extra options). Allow similar option for the `Install` and `Script` commands. This'll allow constructing more generic lists (like user-lists) which will work across different branches and versions.https://gitlab.nic.cz/turris/updater/updater/-/issues/71Order of removal2019-05-06T17:47:11+02:00Ghost UserOrder of removalWhen removing packages, order them inversely by dependencies, so the post/pre-rm scripts are less likely to fail.When removing packages, order them inversely by dependencies, so the post/pre-rm scripts are less likely to fail.https://gitlab.nic.cz/turris/updater/updater/-/issues/70Select the proper candidate2020-11-12T02:24:12+01:00Ghost UserSelect the proper candidateWhen there are multiple candidates to choose from, pick the correct package, not the first one. It would be:
* If the Install request actually asks for something specific (maybe this goes for a future task, because it might be brought i...When there are multiple candidates to choose from, pick the correct package, not the first one. It would be:
* If the Install request actually asks for something specific (maybe this goes for a future task, because it might be brought in as a dependency first)
* Priority of the repository.
* Version number of the package.
* Order of the repositories in the configuration.https://gitlab.nic.cz/turris/updater/updater/-/issues/69Better error reporting2019-05-06T17:47:10+02:00Ghost UserBetter error reportingWhen something fails in the updater-ng, a huge stack trace is output. This is not user-friendly and it would be great to show something understandable (and provide the stack trace to log, or something).When something fails in the updater-ng, a huge stack trace is output. This is not user-friendly and it would be great to show something understandable (and provide the stack trace to log, or something).