Bug 4837 - aMSN is not possible intall
Summary: aMSN is not possible intall
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Jani Välimaa
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-07 10:52 CET by Ojangu
Modified: 2012-03-10 10:42 CET (History)
2 users (show)

See Also:
Source RPM: amsn-0.98.4-7.mga2.x86_64
CVE:
Status comment:


Attachments

Description Ojangu 2012-03-07 10:52:03 CET
Description of problem:aMSN asks gstreamer0.10-farsight2 for installation and without this it isn't install nothing.

Expert says that now amsn rename farsight to farstream.
Manuel Hiebel 2012-03-07 12:31:52 CET

CC: (none) => eandry, mitya
Assignee: bugsquad => jani.valimaa

Comment 1 Dimitri Jakov 2012-03-07 12:41:49 CET
It's me who added "Obsoletes: gstreamer0.10-farsight2" to gstreamer0.10-farstream. The reason was, if gstreamer0.10-farsight2 were installed, then updating to new pidgin would fail (since it's built with Farstream, and gstreamer0.10-farstream conflicts with gstreamer0.10-farsight2). Should we revert it back? In that case, those who want to update to newest pidgin should manually remove gstreamer0.10-farsight2.
Comment 2 Jani Välimaa 2012-03-07 21:31:50 CET
We can rebuild gst-farsight2 and change obsoletes to conflicts in gst-farstream.
Comment 3 Jani Välimaa 2012-03-10 10:42:35 CET
aMSN should be installable now, but you can't have pkgs requiring gstreamer0.10-farsight2 and gstreamer0.10-farstream installed at the same time as those two conflicts each other.

I'm looking how to port aMSN to use farstream instead of old farsight2.

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


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