You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
86c89bf5e8
Conceptually, the compat-version during sysupgrade is meant to describe the config. Therefore, if somebody starts with a device on 19.07 and swconfig, and that person does a forceful upgrade into a DSA-based firmware without wiping his/her config, then the local compat-version should stay at 1.0 according to the config present (and not get updated). However, this poses a problem for those people that early-adopted DSA in master, as they already have adjusted their config for DSA, but it still is "1.0" as far as sysupgrade is concerned. This can be healed by a simple uci set system.@system[0].compat_version="1.1" uci commit system But this needs to be applied _after_ the upgrade (as the "old" fwtool on the old installation does not know about compat_version) and it requires access via SSH (i.e. no pure GUI solution is available for this group of people, apart from wiping their config _again_ for no technical reason). Despite, the situation will not become obvious to those just upgrading via GUI, they will just have the experience of a "broken upgrade". This is a conflict which cannot be resolved by achieving both goals, we have to decide to either keep the strict concept or improve the situation for early adopters. In this patch, we address the issue by providing a uci-defaults script that will raise the compat_version for _all_ people upgrading into a 1.1 image, no matter whether they have reset config or not. The idea is to implement this as a _temporary_ solution, so early adopters can upgrade into the new mechanism without issues, and after a few weeks/months we could remove the uci-defaults script again. If we e.g. remove the script just before 20.xx.0-rc1, early adopters should have moved on by then, and existing stable users would still get the intended experience. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> |
4 years ago | |
|---|---|---|
| .. | ||
| apm821xx | 4 years ago | |
| ar71xx | 4 years ago | |
| arc770 | 4 years ago | |
| archs38 | 4 years ago | |
| armvirt | 4 years ago | |
| at91 | 4 years ago | |
| ath25 | 4 years ago | |
| ath79 | 4 years ago | |
| bcm27xx | 4 years ago | |
| bcm47xx | 4 years ago | |
| bcm53xx | 4 years ago | |
| bcm63xx | 4 years ago | |
| cns3xxx | 4 years ago | |
| gemini | 4 years ago | |
| generic | 4 years ago | |
| imx6 | 4 years ago | |
| ipq40xx | 4 years ago | |
| ipq806x | 4 years ago | |
| ipq807x | 4 years ago | |
| kirkwood | 4 years ago | |
| lantiq | 4 years ago | |
| layerscape | 4 years ago | |
| malta | 4 years ago | |
| mediatek | 4 years ago | |
| mpc85xx | 4 years ago | |
| mvebu | 4 years ago | |
| mxs | 4 years ago | |
| octeon | 4 years ago | |
| octeontx | 4 years ago | |
| omap | 4 years ago | |
| oxnas | 4 years ago | |
| pistachio | 4 years ago | |
| ramips | 4 years ago | |
| rb532 | 4 years ago | |
| rockchip | 4 years ago | |
| samsung | 4 years ago | |
| sunxi | 4 years ago | |
| tegra | 4 years ago | |
| uml | 4 years ago | |
| x86 | 4 years ago | |
| zynq | 4 years ago | |
| Makefile | 4 years ago | |