| Summary: | aMSN is not possible intall | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Ojangu <jaanus.ojangu> |
| Component: | RPM Packages | Assignee: | Jani Välimaa <jani.valimaa> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | eandry, mitya |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | amsn-0.98.4-7.mga2.x86_64 | CVE: | |
| Status comment: | |||
|
Description
Ojangu
2012-03-07 10:52:03 CET
Manuel Hiebel
2012-03-07 12:31:52 CET
CC:
(none) =>
eandry, mitya 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. We can rebuild gst-farsight2 and change obsoletes to conflicts in gst-farstream. 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 |