rpm -Uhv --oldpackage loses configs

[Elan Ruusamäe]

On 07.06.2016 17:31, Jeffrey Johnson wrote:
>> ># ls -l */*pam*
>> >-rw-r--r-- 1 root root 326K  6. juuni 20:17 1465233457/pam-1.1.8-8.x86_64.rpm
>> >-rw-r--r-- 1 root root  35K  6. juuni 20:17 1465233457/pam-libs-1.1.8-8.x86_64.rpm
>> >
>> >root at glen spool/repackage#
>> >root at glen spool/repackage# rpm -Uhv */*pam*  —d
> OK, so repackaged *.rpm were used.
>
> The repackaged rpm’s are “best effort”: if the files are renamed before
> the repackaging occurs, then those packages do not contain the config
> files because the files were not present (on the original path) when the
> repackaging occurred.
come on! the files were removed when i installed from repackage pool. 
(see the log i pasted) NOT BEFORE.
it's RPM that removed (renamed) the files, nothing superficious happened 
before downgrade action removing files. it's all in rpm!


> Do the repackaged rpm’s contain those files.?

the config files are present in .rpm file and in rpmdb where i installed 
the .rpm file:

# rpm -qplvc 1465233457/pam-1.1.8-8.x86_64.rpm|grep auth
-rw-r--r--    1 root    root             1016 veebr 25  2015 
/etc/pam.d/system-auth

# rpm -qc pam|grep /etc/pam.d/system-auth
/etc/pam.d/system-auth

and still marked as %config
> When/how were the repackaged packages created?

this flag was enabled:

root at glen spool/repackage# rpm -E %_repackage_all_erasures
1

and the  repackaged files were created whe pam was upgraded (that pam 
upgrade log is not posted, it's irrelevant and i do not have it)

-- 
glen