Bug 8534

Summary: rpmi -i --force results in package duplication in some cases
Product: Sisyphus Reporter: Mikhail Zabaluev <mhz>
Component: rpmAssignee: placeholder <placeholder>
Status: NEW --- QA Contact: qa-sisyphus
Severity: normal    
Priority: P2 CC: at, glebfm, imz, ldv, mike, n3npq, placeholder, ruslandh, vt
Version: unstable   
Hardware: all   
OS: Linux   
Attachments:
Description Flags
Output of rpmi -ivv --force --justdb pkg-config-0.20-alt2.pentium4.rpm none

Description Mikhail Zabaluev 2005-11-21 14:28:56 MSK 
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!
Comment 1 Mikhail Zabaluev 2005-11-21 14:36:58 MSK 
Created attachment 1260 [details]
Output of rpmi -ivv --force --justdb pkg-config-0.20-alt2.pentium4.rpm
Comment 2 Dmitry V. Levin 2005-11-21 20:57:40 MSK 
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.
Comment 3 Mikhail Zabaluev 2005-11-22 00:10:05 MSK 
4.0.4-alt53 it is.
Comment 4 Michael Shigorin 2009-08-15 14:23:07 MSD 
(In reply to comment #0)
> The obvious workaround to it is: Don't do that!
I'd say WORKSFORME then.
Comment 5 Jeff Johnson 2012-01-02 19:23:48 MSK 
tracked at https://bugs.launchpad.net/rpm/+bug/910871
Comment 6 ruslandh 2024-05-22 09:10:49 MSK 
Имхо давно пора закрыть. 
Это уже не не бага, а багфича  ;-)