rpm -Uhv --oldpackage loses configs

Jeffrey Johnson n3npq at me.com
Tue Jun 7 20:04:35 CEST 2016

> On Jun 7, 2016, at 1:37 PM, Elan Ruusamäe <glen at delfi.ee> wrote:
> here it is:
> https://hub.docker.com/r/glen/rpm-repackage-bug/builds/btjwvf77j6gvmiu67jpbiek/ <https://hub.docker.com/r/glen/rpm-repackage-bug/builds/btjwvf77j6gvmiu67jpbiek/>


If you take out the -h progress bar, the -vv file is easier to read.

The spewage contains

pam                         warning: /etc/security/limits.conf created as /etc/security/limits.conf.rpmnew
warning: /etc/security/namespace.init created as /etc/security/namespace.init.rpmnew

So the install did not install, the remove renamed the existing
modified files with .rpmsave (AFAICT).

ATM, it’s not at all clear how to unsnarl %config handling (which will clobber
existing renamed files). But perhaps something can be done.

Again, my personal belief is that changing/fixing %config handling in RPM,
particularly with —downgrade and repackaging, cannot ever solve the problem
of removed files, or external intervention to rename files. RPM+LIBGIT2 is
a far better way forward.

73 de Jeff

More information about the pld-devel-en mailing list