| Summary: | new package in updates should replace and not keep the older package | ||
|---|---|---|---|
| Product: | Infrastructure | Reporter: | Manuel Hiebel <manuel.mageia> |
| Component: | BuildSystem | Assignee: | Sysadmin Team <sysadmin-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | mailinglistsduraph, sysadmin-bugs |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Manuel Hiebel
2011-10-31 19:57:00 CET
Hi, +1 for this one Other example un Core Updates Debug - kdelibs4-debug 4.6.5-1.1.mga1 - kdelibs4-debug 4.6.5-1.2.mga1 - kdelibs4-debug 4.6.5-1.3.mga1 and if you don't take attention (a long list of updates by example) you select several updates for one package and you have a lovely message like "kdelibs4-debug-4.6.5-1.3.mga1.i586 (en raison de conflit avec kdelibs4-debug-4.6.5-1.2.mga1.i586)". I had this one (very) recently and I first thought a dependancy problem and occupied to open a ticket on bugzilla ... ;-) A+ Raph CC:
(none) =>
mailinglistsduraph ping for repoctl :p So I have check in mdv, only kernel ( and the relative fglrx-kernel-*, etc) are keep. So what about have the same ? |