On Jun 9, 2015, at 5:50 PM, Elan Ruusamäe wrote:
ping jbj?
Yes?
I don't think your change to %config handling is worth the
effort and disruption to the existing %config algorithm.
Grep the code for FA_ALTNAME (for .rpmnew) and FA_BACKUP
(for .rpmorig/.rpmsave) handling, patch as you wish.
On 29.05.2015 00:13, Jeffrey Johnson wrote:
My guess (similar to your previous claim of overwritten) is that package order
ended up as erase-before-install as part of a multiple package upgrade.
yes, pld rpm 4.5 got some (your) patch there eventually.
Was this behavior seen in a multiple
On May 29, 2015, at 4:28 AM, Elan Ruusamäe wrote:
On 29.05.2015 00:13, Jeffrey Johnson wrote:
...
Was this behavior seen in a multiple package upgrade that you have snipped
out?
nop. this was 1 package upgrade:
OK thanks for -vv output.
# rpm -q nagios-nrpe
nagios-nrpe-2.15-1.i686
On 29.05.2015 17:43, Jeffrey Johnson wrote:
I won't make the change in RPM upstream because I believe it's
more important to have consistent %config handling than it is to
preserve unpackaged configuration files on upgrade when the
new (but not the old) package has file content (which almost
On May 25, 2015, at 9:01 AM, Elan Ruusamäe wrote:
again rpm is ovewriting existing files, not creating them as .rpmnew when the
file is new in the package itself.
Claiming overwriting is premature (see below).
imho this got solved at least in 4.5...
Comparisons to rpm-4.x behaviors
