Bug 17064

Summary:	task-obsolete in Mga5 has different versions in core and tainted
Product:	Mageia	Reporter:	Barry Jackson <zen25000>
Component:	RPM Packages	Assignee:	QA Team <qa-bugs>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	jani.valimaa, lewyssmith, sysadmin-bugs, westel
Version:	5	Keywords:	validated_update
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:	advisory MGA5-64-OK, mga5-32-ok
Source RPM:	task-obsolete	CVE:
Status comment:

Description Barry Jackson 2015-11-02 20:34:06 CET

Description of problem:
The content of task-obsolete is different in Mageia 5 tainted to that in core.
The package appears to have been incorrectly branched for Mageia5, such that a fictional release was added to the core version of 109, and it was not pushed to tainted.

[baz@localhost ~]$ urpmq -f task-obsolete
task-obsolete-5-109.mga5.noarch|task-obsolete-5-41.mga5.tainted.noarch

This breaks updates for some packages (with tainted enabled) by forcing removal of packages that were removed from task-obsolete in core.

To fix this and bring both into sync, new packages have been pushed to both core and tainted updates_testing.

##############################
Update Advisory:

task-obsolete-5-109.1.mga5 has been submitted to 5/core/updates_testing and
to 5/tainted/updates_testing.

This corrects an out of sync between the two repositories which was causing update issues with some packages.

See https://bugs.mageia.org/show_bug.cgi?id=1067#c32 and following comments for reference.

##############################
Packages affected:

task-obsolete-5-109.1.mga5.noarch.rpm
task-obsolete-5-109.1.mga5.tainted.noarch.rpm

##############################
Testing:

Probably not required, but the scenario in the referred bug would be an example, which I will test again with updates_testing enabled

##############################

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:

Barry Jackson 2015-11-02 20:37:21 CET

Assignee: bugsquad => qa-bugs
Severity: major => normal

Barry Jackson 2015-11-02 20:48:54 CET

CC: (none) => jani.valimaa

Comment 1 Lewis Smith 2015-11-06 15:16:20 CET

Testing Mageia 5 x64, OK.

Playing solely with urpmq (which I was quite unable to make do what it says; specifically --sources Prints source URLs (or file names) of all selected packages), with Core Release/Nonfree/Tainted enabled (but NOT their Updates Testing equivalents), it showed [unimportant lines removed]:
# urpmq -i task-obsolete
Name        : task-obsolete
Version     : 5
Release     : 109.mga5
Source RPM  : task-obsolete-5-109.mga5.src.rpm

Name        : task-obsolete
Version     : 5
Release     : 41.mga5.tainted
Source RPM  : task-obsolete-5-41.mga5.tainted.src.rpm

The basis of the bug: the release-IDs are different.
With both release & updates testing repos enabled, the output was a combination of that above and that below - but with no indication of the origin of each package.

With Core/Nonfree/Tainted Updates Testing enabled (but NOT their release equivalents):
# urpmq -i task-obsolete
Name        : task-obsolete
Version     : 5
Release     : 109.1.mga5
Source RPM  : task-obsolete-5-109.1.mga5.src.rpm

Name        : task-obsolete
Version     : 5
Release     : 109.1.mga5.tainted
Source RPM  : task-obsolete-5-109.1.mga5.tainted.src.rpm

which demonstrates that in the repositories, the updated packages now have the same release-ID (5-109.1).

CC: (none) => lewyssmith
Whiteboard: (none) => MGA5-64-OK

Comment 2 claire robinson 2015-11-06 16:19:03 CET

Verified versions now in sync with an old friend..

$ ./depcheck task-obsolete
Mageia release 5 (Official) for x86_64
------------------
Core 32bit Release
task-obsolete-5-109.mga5
------------------
Core Release
task-obsolete-5-109.mga5
------------------
Core Updates Testing
task-obsolete-5-109.1.mga5
------------------
Tainted 32bit Release
task-obsolete-5-41.mga5.tainted
------------------
Tainted Release
task-obsolete-5-41.mga5.tainted
------------------
Tainted Updates Testing
task-obsolete-5-109.1.mga5.tainted
------------------

Comment 3 Ben McMonagle 2015-11-07 06:05:55 CET

same test procedure as provided by Lewis in comment #1

result for i586: 

# urpmq -i task-obsolete
Name        : task-obsolete
Version     : 5
Release     : 109.1.mga5
Source RPM  : task-obsolete-5-109.1.mga5.src.rpm


Name        : task-obsolete
Version     : 5
Release     : 109.1.mga5.tainted
Source RPM  : task-obsolete-5-109.1.mga5.tainted.src.rpm

CC: (none) => westel
Whiteboard: MGA5-64-OK => MGA5-64-OK, MGA5-32-OK

Ben McMonagle 2015-11-07 06:06:36 CET

Whiteboard: MGA5-64-OK, MGA5-32-OK => MGA5-64-OK,

Comment 4 claire robinson 2015-11-07 17:53:08 CET

Adding OK from Ben's test & Validating. Thanks.

Keywords: (none) => validated_update
Whiteboard: MGA5-64-OK, => MGA5-64-OK, mga5-32-ok
CC: (none) => sysadmin-bugs

Comment 5 claire robinson 2015-11-07 18:18:50 CET

Advisory uploaded with core and tainted srpms.

src:
  5:
   core:
     - task-obsolete-5-109.1.mga5
   tainted:
     - task-obsolete-5-109.1.mga5.tainted

Whiteboard: MGA5-64-OK, mga5-32-ok => advisory MGA5-64-OK, mga5-32-ok

Comment 6 Mageia Robot 2015-11-07 21:12:11 CET

An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGAA-2015-0176.html

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

Comment 7 Barry Jackson 2015-11-15 15:43:05 CET

Hmmm. seems this failed to solve the issue.

[baz@localhost ~]$ urpmq -i task-obsolete|grep Release
Release     : 109.mga5
Release     : 109.1.mga5
Release     : 41.mga5.tainted
Release     : 109.1.mga5.tainted

from urpmi --auto-update
selecting task-obsolete-5-41.mga5.tainted.noarch

[baz@localhost opencpn]$ urpmq --list-media active
Core Release (zmrepo1)
Core Updates (zmrepo3)
Nonfree Release (zmrepo11)
Nonfree Updates (zmrepo13)
Tainted Release (zmrepo21)
Tainted Updates (zmrepo23)
srpms
Core Release Debug (distrib2)

Comment 8 Barry Jackson 2015-11-15 16:25:28 CET

However the above is with no version of task-obsolete installed, which is default for a new install.

urpmi-task-obsolete

does pull the new version and thereafter 

urpmi --auto-update

works OK using the installed version.