Bug #6958
closed
RPM package install doesn't report properly if there is twice the same package
Added by Benoît PECCATTE over 9 years ago.
Updated about 8 years ago.
Description
which happens when you want install+update or when you have a lot of directive and one with update and another one with "not this version"
- Target version changed from 2.11.13 to 2.11.14
- Target version changed from 2.11.14 to 2.11.15
- Target version changed from 2.11.15 to 2.11.16
- Target version changed from 2.11.16 to 2.11.17
- Target version changed from 2.11.17 to 2.11.18
- Target version changed from 2.11.18 to 2.11.19
- Target version changed from 2.11.19 to 2.11.20
- Target version changed from 2.11.20 to 2.11.21
- Target version changed from 2.11.21 to 2.11.22
- Target version changed from 2.11.22 to 2.11.23
- Target version changed from 2.11.23 to 2.11.24
- Target version changed from 2.11.24 to 308
- Status changed from New to Rejected
- Is duplicate of Bug #8034: When we manage twice a same package in rpm package management, we don't get the second report added
- Target version changed from 308 to 3.1.14
Also available in: Atom
PDF
Updated by 
Updated by