Bug 1638 - Mageia Update does not list updates from tainted repositories
Summary: Mageia Update does not list updates from tainted repositories
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-06 14:59 CEST by Thomas Lottmann
Modified: 2014-05-08 18:05 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Thomas Lottmann 2011-06-06 14:59:13 CEST 
Kernel version = 2.6.33.7-desktop-2mnb
Distribution=Mageia release 1 (Official) for x86_64
CPU=Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz

Mageia Update does not list the updates from the tainted repositories, not more does the Mageia Online update applet does notify me of updates. 

These updates appear clearly in the All updates list in RPMDrake. 

Thank you.
Comment 1 Nicolas Vigier 2011-06-06 15:15:10 CEST 
There is currently no updates in the tainted repository.

CC: (none) => boklm

Comment 2 James Kerr 2011-06-06 15:39:14 CEST 
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.)
Comment 3 Ahmad Samir 2011-06-06 20:22:39 CEST 
James is right, I think.

Closing.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 4 Thomas Lottmann 2011-06-07 15:16:00 CEST 
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)
Note You need to log in before you can comment on or make changes to this bug.