-
Notifications
You must be signed in to change notification settings - Fork 96
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
Sysupgrade preserving lime-defaults config problems #706
Comments
First proposed solution sounds good. |
Yes, first proposal is the way to go imho. You can easily tell UCI to use an alternative configuration directory (we are already doing that in places, ie. for |
great (yes, in the unittests we are also faking the config directory creating an empty environment for each test)
Ah, didn't know that. Anyway this is a problem because not only we are modifying them from lime-config but also some are created durin first boot. This leads to many problems while upgrading to different versions of openwrt. With @germanferrero we worked in a proposal to aproach configs in libremesh that will allow easier maintenance and it is related to this issue #719 |
Fixed in #738 |
Currently using
sysupgrade
(or safe-upgrade) to upgrade a firmware while preserving configurations overwrites unexpectedly the firmware/etc/config/lime-defaults
with the currentlime-defaults
so it is not possible to provide a new default without using-n
option of sysupgrade.This happens because
/lib/upgrade/keep.d/base-files
provided by openwrt contains the following line/etc/config/
. So all all /etc/config files are backup and preserved (including lime-defaults).This leads to the following error after upgrading:
There are multiple ways to fix. Some ideas:
/usr/share/lime/config
directory (to more clearly imply that this file should not be edited).The text was updated successfully, but these errors were encountered: