[bug] Changed configuration files get overwritten during updates
Obviously, they shouldn't be overwritten. Even opkg doesn't overwrite changed configuration files.
We have moved to a new Sailfish OS Forum. Please start new discussions there.
Obviously, they shouldn't be overwritten. Even opkg doesn't overwrite changed configuration files.
This thread is public, all members of Together.Jolla.Com can read this page.
Asked: 2020-05-01 18:15:52 +0200
Seen: 81 times
Last updated: May 01 '20
[Fixed in 1.0.3.8] Crash when linking contacts? [not relevant]
Time slider usage in video player of Gallery app causes the app to hang [duplicate]
QAudioOutput isn't integrated with system volume and libresource like QMediaPlayer
During system updates are downloads kept to a minimum?
Bug: E-Mail synchronization does not work as configured [released]
Word prediction should be always turned off when entering passwords in Android apps [released]
Don't enforce focus to textfield [answered]
[Implemented in 1.0.3.8] Email: Honour Reply-To header [answered]
Each RPM specifies (per spec file), if it overwrites (default), backups or retains individual configuration files when updated.
This is how RPM works (i.e., on all Linux distributions utilising RPM).
So you may address this as an issue for the specific RPM you had issues with (e.g. at git.sailfishos.org).
olf ( 2020-05-01 20:25:18 +0200 )editSide note: Usually the RPM's (spec file) authors had reasons to set a specific behaviour (or not) for a configuration file.
The overwritten files belong to droid-system-vendor-voyager package. I'll try to make a pullrequest when I'll have free time, I see no problem with config files marked config(noreplace), since files won't be owerwritten only if they were changed.
0xe4524ffe ( 2020-05-05 19:33:43 +0200 )edit