When file conflicts are enabled, the computation is inconsistent. Given packages that traditionaly have conflicts (non-ELF files are different), when conflicts are reported depends on the transaction set is involved. Testing was done with octave, other packages will satisfy. 1) both 32 and 64 bit versions of the package in the transaction set - no conflicts reported 2) install 32 when 64 bit is present - conflicts reported 3) install 64 when 32 bit is present - conflicts reported
So you wish added+added to have same behavior as added+installed (both cases)? Or vice versa? Please state your expectation precisely.
Added+added behavior matching the current added + installed behavior is what makes sense to me. (i.e., #1 matches #2 and #3.)
OK, tnx. I'm not sure rpm ever got this right ;-) I'll get file conflicts foxed soon sfter deploops are stabilized ...
AFAICR, this bug was foxed over a year ago. Reopen if not.