New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#826 - Better implementation of upgrade system on lede #6384
Comments
diizzyy: Not doable due to how the overlay file system works |
pietia: Hi, So basically what we need to do using opkg upgrade is : sysupgrade -v /tmp/filename-of-downloaded-sysupgrade.bin (this ensures that our config are saved) Altought it's not ideal and not very debian-like that's in my opinion the easiest way to add this feature. |
yousong: Preserving and fallback to old kernel is not an easy thing to implement for most devices supported by LEDE. I guess the feature you are requesting is more about reinstalling those packages "requested" by users after flashing the released firmware. To achieve this, we need to modify opkg to keep such info. It's a good-to-have feature, but again for small devices with limited computing and storage resources, the feature seems to me to be not that urgent and attractive. |
pietia: Hello, |
yousong: A simple solution can be
# before sysupgrade
opkg list-installed | cut -f1 -d' ' >old
# after sysupgrade
opkg list-installed | cut -f1 -d' ' >new
# find the diff
sort old new | uniq -u >requested-and-their-deps
But usually I only have one or two extra packages installed after sysupgrade, so I don't need to bother to go such length to figure them out... It's not like in debian where I build the environment incrementally over time. The boxes I have LEDE on are mostly of one-time setup and serve all the time type. |
pietia: Yeah same here , but the idea is to have simpler upgrades without any user interaction besides typing opkg upgrade just like in debian. |
pepe2k: Take a look at this GSoC 17 project: |
aparcar: Hello, My approach tries to auto generate sysupgrade images on demand based on installed packages. |
pietia: Hi Aparcar, Using my approach can be coded in hour and it's based on already written sysupgrade program I'm not sure only where can we add to install packages from file post sysupgrade, except generating that big json file with 750 routers this can take hours .(but every release we just replace all in links 17.0.1 for example for 17.0.2 and if all paths are same it will be one minute work.) Perhaps there is some conf that stores openwrt-kirkwood-linksys-viper-squashfs instead of board.json: "id": "linksys-viper" |
clel: I came here, because I also want an easier approach of upgrading. The approach from Freifunk looks interesting, especially that it can be done via GUI. Additionally I'd suggest to do an automated checksum check before installing. |
aparcar: The checksum check is planned, thanks for the reminder! |
clel: Nice. Now I also found the GitHub repo for this (https://github.com/aparcar/attendedsysupgrade-server) Is this already working and will it get integrated by default to future LEDE versions? |
clel: @felix Fietkau |
pietia:
Hi,
It would be good to have an better implementation of upgrade system on lede , I'm talking about debian-like update system so for example after doing :
opkg update, opkg upgrade
it would upgrade all packages including kernel to the latest stable release of lede and leave one old kernel (it's for getting back to old kernel if anything goes wrong)
After that reboot and we are in newest kernel.
The text was updated successfully, but these errors were encountered: