The documentation states that --force is a shorthand for --replacefiles --replacepkgs --oldpackage. However, installing a package over the same, but different package(1) with --force leads to duplicate package entries in the rpm database. (1) I got this result when a package had the same name, version, release, and epoch, but differed in other fields, such as Provides. Installing a package over itself doesn't have this effect. The obvious workaround to it is: Don't do that!
Created attachment 1260 [details] Output of rpmi -ivv --force --justdb pkg-config-0.20-alt2.pentium4.rpm
Are you talking about rpm >= 4.0.4-alt53? I'm unable to reproduce this behavior. BTW, changes in rpm-4.0.4-alt53 make --force option less needed than before, because -U and -F options now take build dates into account.
4.0.4-alt53 it is.
(In reply to comment #0) > The obvious workaround to it is: Don't do that! I'd say WORKSFORME then.
tracked at https://bugs.launchpad.net/rpm/+bug/910871
Имхо давно пора закрыть. Это уже не не бага, а багфича ;-)
