Bug 22324

Summary:	MGA 6 GUI system update (drakerpm) not listed updates from tained repo like VLC tained
Product:	Mageia	Reporter:	AngryPenguin <xpris>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	jim, marja11
Version:	6
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description AngryPenguin 2018-01-05 19:24:51 CET

Description of problem:

Hi. After fresh MGA6 install, added repository and also enabled tained repo. 
Trying update system and it update all packages without packages from tained repository.

This is only when I use GUI updater (rpmdrake). In console urpmi --auto-update listing all remains packages from tained but GUI show me that no packages to update.

Steps to Reproduce:
1. Install MGA6 x64
2. Enable tained repository
3. Update system via GUI (rpmdrake)
4. After update check it again and see - no updates available
5. Check now for updates in terminal - urpmi --auto-update it find packages for update from tained repo.

See screenshot:
https://imgur.com/a/BMrB6

Comment 1 James Kerr 2018-01-05 20:43:47 CET

That's because mageia-update (the updater) only looks for updates in repo's that are marked as update sources.

To replace installed core packages with their tainted versions, you can either use "urpmi --auto-update" from the CLI 

or open "Install and remove software" and select "All Updates" from the first drop-down filter 

or use "drakrpm-editmedia --expert" and tag tainted-release as an update source and run mageia-update

To have mageia-update always look in tainted-release for tainted versions of installed core packages perhaps might be a useful enhancement, but it would only be needed once, after enabling the tainted repo, and the negative performance effect on mageia-update might be undesirable.

CC: (none) => jim

Comment 2 AngryPenguin 2018-01-05 22:31:41 CET

Thanks for explaining.

Comment 3 Marja Van Waes 2018-01-07 08:24:54 CET

(In reply to AngryPenguin from comment #2)
> Thanks for explaining.

So James was right, and it was just a media configuration error, right?

Please reopen this bug report if that was not the case.

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