Bug 12430

Summary:	nagios-check_netapp is present twice in core/release
Product:	Mageia	Reporter:	Samuel Verschelde <stormi-mageia>
Component:	Release (media or process)	Assignee:	Sysadmin Team <sysadmin-bugs>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	release_blocker	CC:	guillomovitch, mageia, pterjan, sysadmin-bugs, thierry.vignaud
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	nagios-plugins	CVE:
Status comment:
Bug Depends on:
Bug Blocks:	11704

Description Samuel Verschelde 2014-01-25 13:11:33 CET

nagios-check_netapp-1.4.16-9.mga4.i586.rpm
nagios-check_netapp-20060619-6.mga4.noarch.rpm

Reproducible: 

Steps to Reproduce:

Samuel Verschelde 2014-01-25 13:14:32 CET

Priority: Normal => release_blocker
Blocks: (none) => 11704

Comment 1 Colin Guthrie 2014-01-26 16:01:28 CET

So this is provided by both a standalone package, and as part of the nagios-plugins package.

The file from this one is larger, so my naive analysis would suggest it's better.

Perhaps this package should just be renamed?

CC: (none) => guillomovitch, mageia

Comment 2 Thierry Vignaud 2014-01-26 18:20:58 CET

Likely a bug due to arch vs noarch change

CC: (none) => pterjan, thierry.vignaud

Comment 3 Pascal Terjan 2014-01-26 19:02:07 CET

The arch vs noarch probably explains why nagios-plugins doesn't get rejected when it is uploaded with an older version but still,two src.rpm shouldn't generate the same package.

Comment 4 Samuel Verschelde 2014-01-27 15:33:34 CET

So, according to discussion on dev ML, the one that should be removed is:

nagios-check_netapp-20060619-6.mga4.noarch.rpm, which is a standalone old package. 1.4.16 is actually 1:1.4.16 so there will be no upgrade problem. People should already have the good one, it's just a matter of cleaning the repo before freezing it.

Comment 5 Colin Guthrie 2014-01-27 16:08:04 CET

OK, so this has now been removed from SVN:

------------------------------------------------------------------------
r568254 | guillomovitch | 2014-01-26 17:02:48 +0000 (Sun, 26 Jan 2014) | 2 lines

old and unmaintained script



And I've now removed the package from the tree too. Next package upload will nuke it from metadata.

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