[DOCS-3383] Investigate config file change management with debian packages Created: 09/May/14  Updated: 16/Mar/15  Resolved: 11/Feb/15

Status: Closed
Project: Documentation
Component/s: Cloud Manager
Affects Version/s: None
Fix Version/s: v1.3.18

Type: Task Priority: Major - P3
Reporter: Bob Grabar Assignee: Andrew Aldridge
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 9 years, 1 week ago

 Description   

Figure out how debian does change resolution for packaged config files.

This affects:
/includes/steps-upgrade-on-prem-with-deb-packages



 Comments   
Comment by Andrew Aldridge [ 11/Feb/15 ]

dpkg's conffile behavior is described here, and is pretty much the same as RPM and pacman's behavior.

> If neither the user nor the package maintainer has changed the file, it is left alone.

> If one or the other has changed their version, then the changed version is preferred - i.e., if the user edits their file, but the package maintainer doesn't ship a different version, the user's changes will stay, silently, but if the maintainer ships a new version and the user hasn't edited it the new version will be installed (with an informative message).

>If both have changed their version the user is prompted about the problem and must resolve the differences themselves.

Generated at Thu Feb 08 07:45:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.