| Summary: | rpmdrake search does not check core-updates if it is listed before core in urpmi.cfg | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | James Kerr <jim> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins |
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | rpmdrake-5.49-1.mga3.src.rpm | CVE: | |
| Status comment: | |||
| Attachments: |
search for not installed package
search after installing package |
||
|
Description
James Kerr
2013-10-16 18:02:40 CEST
Created attachment 4439 [details]
search for not installed package
This shows the search result for a package that is not installed
Created attachment 4440 [details]
search after installing package
This shows the search result immediately after installing the 64 bit package found in the first search.
urpmi does find the package in core-updates even before the core package is installed: urpmi --test plasma-wallpaper-weather installing plasma-wallpaper-weather-4.10.5-1.1.mga3.x86_64.rpm I have just noticed that core-updates was listed in /etc/urpmi/urpmi.cfg before core. Changing the order of the repo's in urpmi.cfg, so that core is listed before core-updates corrects the problem reported here. I was not aware that the order in which the core and core-updates repo's are listed in urpmi.cfg would make this difference. If this is the expected behaviour then I suppose that this bug can be treated as invalid, but I don't think that I have ever seen advice that the order in which the repo's are listed in urpmi.cfg can have this sort of effect in rpmdrake. The question is, how did they get added in the wrong order? Depending on when they were added, this may be a duplicate of bug 10355. CC:
(none) =>
davidwhodgins media.cfg looks ok if you add it with the "--distrib" option ie http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/3/x86_64/media/media_info/media.cfg Assignee:
bugsquad =>
thierry.vignaud I suppose that it is possible that the order of the repo's is a result of bug #10335, but I see no other oddity in my urpmi.cfg. It's possible that I set up the updates repo's first. (IIRC there was an early update to urpmi.) Then after adding a full set of repo's using --distrib, deleted the core-updates that was added, instead of the one created earlier. I have no clear recollection of actually doing it. (These days my memory is not reliable.) None of that explains why the order of the repo's seems to have the effect that it does on the rpmdrake search function. It could be that the order has always been critical and I have just never experienced this issue before. (In reply to Manuel Hiebel from comment #7) I don't think that the problem stems from media.cfg and so have clarified the subject of this bug. The issue that this bug addresses is whether the order of the repo's in urpmi.cfg should have the effect on the rpmdrake search function that it seems to do. If the order of the repo's in urpmi.cfg is intended to be critical, then I think that this bug can be dismissed as due to user error. :) Summary:
rpmdrake search does not check core-updates (updates before release in media.cfg) =>
rpmdrake search does not check core-updates if it is listed before core in urpmi.cfg Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad Status:
NEW =>
RESOLVED |