| Summary: | Mageia Update does not list updates from tainted repositories | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Thomas Lottmann <skiperdrake> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Thomas Lottmann
2011-06-06 14:59:13 CEST
There is currently no updates in the tainted repository. CC:
(none) =>
boklm If you mean that you want a package in /tainted/release to be selected by Mageia Update as an update to an equivalent package in /core/release, then I think that you need to tag /tainted/release as an updates source. (Mageia Update only uses sources tagged as update sources.) James is right, I think. Closing. Status:
NEW =>
RESOLVED James is indeed right. I completely forgot about the possibility that the packages were equivalents. All my apologies.
Nicolas Vigier
2014-05-08 18:05:10 CEST
CC:
boklm =>
(none) |