On Apr 19, 2016, at 4:59 PM, Elan Ruusamäe wrote: > i'm pretty sure this has happened before, just did not payed attention >
I believe you. Meanwhile ... > so, if i use --nodeps rpm forgets it has to put .rpmnew? > and instead no config files left on the original path (mv -i would had said > that file is there) > RPM verifies dependency assertions and then installs files from packages. Adding --nodeps disables dependency assertion verification, while %config file resolution (like renaming to *.rpmnew) is computed while installing. These actions are largely indpendent of each other, based on different package data. Something else is going on imho. > there are no %file %config changes between the versions in the transaction > And the %config file resolution in rpm has not changed in many years, like all of this century. > don't want to re-test this, but seems like it > I cannot do engineering based on anecdotal inattention to details. The minimum necessary information necessary for a rpm bug report about %config needs a reproducer with rpm, not poldek, using -vv to output the %config file renaming computed by rpmlib and a clear statement of what specific behavior you are claiming that is broken. hth 73 de Jeff _______________________________________________ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en