| Summary: | urpmi.update spends useless time on disabled medias | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Thomas Backlund <tmb> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins, eeeemail, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | urpmi | CVE: | |
| Status comment: | |||
|
Description
Thomas Backlund
2013-10-26 16:20:51 CEST
this could explain https://bugs.mageia.org/show_bug.cgi?id=11478 mgaapplet updates disabled backport repo's. IIRC,this is done so that the second filter in rpmdrake can display backports when the backports repo's are not enabled. In the Mandriva days there was a (lengthy) discussion about how backports should be handled by rpmdrake: https://qa.mandriva.com/show_bug.cgi?id=40556 Correction - it's the first filter in rpmdrake that is intended to display backports. Yeah, but from what I saw it seems to probe every disabled mediam including debug, testing, 32bit, ... Workaround would be to remove all unwanted media, instead of just disabling them. urpmi.removemedia -y BackPorts Same for Debug, Testing, and for most cauldron users Updates. CC:
(none) =>
davidwhodgins
claire robinson
2013-10-28 08:43:30 CET
CC:
(none) =>
eeeemail Is this bug still valid? Until today I had to kill 2 instances of mgaapplet and then urpmi.update (first killing urpmi.update didn't work, because it was started again right away), before I could run "urpmi --auto-update". The problem seems solved now. My uptime is 32 minutes, only one mgaaplet is running (sleeping now) and no urpmi.update I don't get the message about the locked urpmi database any more CC:
(none) =>
marja11 |