Actions
Bug #8286
closedncf package asks about replacing dist config file during upgrade
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
From an upgrade on Debian 7 to ncf 1.0.0.201604132224-wheezy1:
Setting up ncf (1.0.0.201604132224-wheezy1) ... Configuration file `/usr/share/ncf/tree/ncf.conf' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** ncf.conf (Y/I/N/O/D/Z) [default=N] ? d
This doesn't make any sense because this is the version in /usr/share, aka the "dist" version. It shouldn't be used in local installs anyway, so we should freely overwrite it.
Updated by Jonathan CLARKE over 8 years ago
- Project changed from 41 to Rudder
- Category set to Packaging
- Target version set to 2.11.21
Updated by Jonathan CLARKE over 8 years ago
- Status changed from New to In progress
Updated by Jonathan CLARKE over 8 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/927
Updated by Jonathan CLARKE over 8 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-packages|8a8de3224e4ea3df39bc5077e360b689dcaff27c.
Updated by Vincent MEMBRÉ over 8 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.21, 3.0.16, 3.1.10 and 3.2.3 which were released on 2016-06-01, but not announced.
- 2.11: Changelog
- 3.0: Changelog
- 3.1: Changelog
- 3.2: Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions