Bug 15842 - Lib64gamin problem during installation.
Summary: Lib64gamin problem during installation.
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-04 16:36 CEST by Jude Ashvin Lobo Shenoy
Modified: 2015-05-04 17:47 CEST (History)
2 users (show)

See Also:
Source RPM: lib64gamin
CVE:
Status comment:


Attachments
There was a problem when installing lib64gamin. (91.96 KB, image/png)
2015-05-04 16:37 CEST, Jude Ashvin Lobo Shenoy
Details
urpmq --list-url (17.83 KB, application/vnd.oasis.opendocument.text)
2015-05-04 17:43 CEST, Jude Ashvin Lobo Shenoy
Details

Description Jude Ashvin Lobo Shenoy 2015-05-04 16:36:43 CEST
Just got an update for lib64gamin so went ahead with the update and then i get a popup that says "There was a problem during the installation". Am having this issue from the last 2 days. A snapshot is attached.
Jude Ashvin Lobo Shenoy 2015-05-04 16:36:58 CEST

Source RPM: (none) => lib64gamin

Comment 1 Jude Ashvin Lobo Shenoy 2015-05-04 16:37:38 CEST
Created attachment 6442 [details]
There was a problem when installing lib64gamin.
Comment 2 Samuel Verschelde 2015-05-04 16:58:41 CEST
The package you are trying to install has been removed from cauldron repositories years ago, for Mageia 3.

What's the output of urpmq --list-url ?

CC: (none) => anssi.hannula

Jani Välimaa 2015-05-04 17:12:06 CEST

CC: (none) => jani.valimaa

Comment 3 Jude Ashvin Lobo Shenoy 2015-05-04 17:43:17 CEST
Created attachment 6443 [details]
urpmq --list-url
Comment 4 Jude Ashvin Lobo Shenoy 2015-05-04 17:44:00 CEST
Hi Samuel,

Attached please find the file with the output of the above command.
Comment 5 Samuel Verschelde 2015-05-04 17:47:01 CEST
You've got a mix of Mageia 2 and Mageia cauldron media. Removed them all and add cauldron media back, everything will be fine.

Closing as INVALID since it is not a bug, but still glad to have helped.

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


Note You need to log in before you can comment on or make changes to this bug.