| Summary: | qt4-examples-4.8.2 will not install on update from MGA1 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Bill Wilkinson <wrw105> |
| Component: | RPM Packages | Assignee: | Nicolas Lécureuil <mageia> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins, qa-bugs, sysadmin-bugs, tmb, wrw105 |
| Version: | 2 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | qt4 | CVE: | |
| Status comment: | |||
|
Description
Bill Wilkinson
2012-09-07 18:59:04 CEST
does it work not better with urpmi ? Keywords:
(none) =>
NEEDINFO It hadn't with the updates in MCC, just tried urpmi qt4* in the same directory and got the same error. CC:
(none) =>
wrw105 nicaloas, something that you can fix ? Assignee:
bugsquad =>
nicolas.lecureuil As a follow-up: Using install and remove software in MCC (unchecking the old version from MGA1 and checking the new version) appears to resolve the issue. QT4 examples is now updated. Bug 2317 catches us again. Could someone from the sysadmin team link the rpm packages from Mageia 2 Core Release to Core Updates lib64gphoto2-2.4.11-4.mga2 (Core Release (distrib1)) libgphoto-common-2.4.11-4.mga2 (Core 32bit Release (distrib31)) libgphoto-common-2.4.11-4.mga2 (Core Release (distrib1)) Our automated script for trying to catch this type of problem failed, when the update for bug 6656 was tested, as these packages are also in Core Updates Testing (since Aug. 31st), though no bug report appears to have been assigned to qa for the updates. Keywords:
NEEDINFO =>
validated_update Packages linked. Status:
NEW =>
RESOLVED |