Bug 15535

Summary:	M5RC i586 Cinnamon. when attempting to install flash player plugin via Mageia Welcome, install fails
Product:	Mageia	Reporter:	Ben McMonagle <westel>
Component:	RPM Packages	Assignee:	Daniel Napora <napcok>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	mageiawelcome	CVE:
Status comment:

Description Ben McMonagle 2015-03-20 11:28:05 CET

Description of problem: when attempting to install Flash-player-plugin via Mageia Welcome , the install fails with a "An error occurred:
ERROR: 'script' failed for flash-player-plugin-11.2.202.280-1.mga3.nonfree " window. 
Attempting the install from within MCC appears to complete, but a search for "flash-player-plugin " it is not listed as installed.
there is no advisory that the install fails in this instance


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

flash-player-plugin-11.2.202.280-1.mga3.nonfree


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:

Comment 1 David Walser 2015-03-20 20:52:36 CET

Obviously 11.2.202.280-1.mga3 is a hardcoded version of an old Mageia 3 package.  I guess it's coming from mageiawelcome, which shouldn't be hardcoding a version.

Assignee: bugsquad => napcok
Source RPM: flash-player-plugin-11.2.202.280-1.mga3.nonfree => mageiawelcome

Comment 2 Daniel Napora 2015-04-21 13:02:08 CEST

Mageiawelcome don't have any package version hardcoded. It uses what is in configured medias, doing "gurpmi packagename". So you probably have old mageia 3 repositories enabled.

Comment 3 Ben McMonagle 2015-04-21 21:55:36 CEST

the install was a fresh cauldron install that had formatted ./ and /home
online media were set up via MCC gui, " mirrorlist " 
This - flash-player-plugin - was the only package that was affected,
others software installed without issue.

as this was a one off, and M5RC has not exhibited the issue since, I would suggest that this bug is closed.

Comment 4 Daniel Napora 2015-04-21 22:48:55 CEST

So I changed status to Resolved Invalid

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