Button in LuCi to install overlay packages defined in installed_packages.txt
See original GitHub issueIt is now possible with sysupgrade to get a list of your user installed packages (on the overlay) and have this put in installed_packages.txt
which is preserved during a firmware upgrade.
However there appears to be no easy way to install these missing packages (for newbies) so what I purpose is putting a button on the Backup / Flash Firmware
page to allow end-users with one click to install these missing packages (assumes working internet).
It would also be useful to have the option to create the installed_packages.txt
and update it if required when generating a config backup
relates to https://github.com/openwrt/luci/issues/4160
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Show available package upgrades after SSH login - OpenWRT
Show available package upgrades after SSH login Blindly upgrading packages (manually or via script) can lead you into all sorts of trouble.
Read more >Is there a simple way to upgrade your packages using luci?
You can manually update packages but you ahve to do it one by one. There is no upgrade all button. This can be...
Read more >The OpenWrt upgrade process - onemarcfifty
An upgrade of OpenWrt can be done in many ways - Upgrade with LuCi, Upgrade with sysupgrade or Upgrade OpenWrt with the new...
Read more >github source openwrt-18.06 branch - Onion Community
Is it possible to install kmods that are not compiled by Onion without ... Done The following additional packages will be installed: nodejs ......
Read more >Highspeed VPN Router With Raspberry Pi - Instructables
1. On a Windows machine, download and install Etcher
Download latest OpenWRT image (rpi-4-ext4-factory.img.gz) for Raspberry Pi 4
Use Etcher to flash the ... 2....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In the real world, it just works. I’ve been doing that since before 19.07 when -k was upstreamed. If a failed package installation does not prevent others to be installed, it might work as expected. OpenWrt repos do not keep old versions. So, if a package is simply an old requirement and it is now missing, the real software will require the correct dependency.
I’m just more cautious between major release upgrades. I normally simply ignores all lib* packages during that reinstall, as it might include unnecessary packages, and let the system download the recent dependency. With minor releases, I simply do a blind “install all”. Excluding reboot/download/install times, it take me less than a minute of attention for each upgrade.
I believe that Luci should not be the one responsible for coding that. It should be a standalone utility/service/hotplug script, probably optionally enabled during backup by a sysupgrade flag. For now, I wrote a “reinstall” reinstall.gz script that I’m carrying between upgrades (‘sysupgrade -o’). It is not ready for upstream but it does get the job done. I manually run it after each upgrade, saving me a lot of time. It has a primitive text-based interface and it will do nothing you didn’t asked it to do.
The button could run something like
Taken from here https://www.mail-archive.com/openwrt-devel@lists.openwrt.org/msg43129.html