Bug 8372 - evolution sharp cannot be installed due to missing dependencies
Summary: evolution sharp cannot be installed due to missing dependencies
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-12 15:28 CET by Jérôme Dern
Modified: 2014-11-01 00:05 CET (History)
2 users (show)

See Also:
Source RPM: evolution-sharp-0.21.1-13.mga2.src.rpm
CVE:
Status comment:


Attachments

Description Jérôme Dern 2012-12-12 15:28:17 CET
Evolution-sharp cannot be installed :

[root@localhost jerome]# LC_ALL=C urpmi evolution-sharp
A requested package cannot be installed:
evolution-sharp-0.21.1-13.mga2.i586 (due to unsatisfied libebook-1.2.so.13)
Continue installation anyway? (Y/n) n

The rebuild on the package seems to have failed, and evolution-sharp have already been dropped from Fedora for that reason (multiple ftbfs : http://pkgs.fedoraproject.org/cgit/evolution-sharp.git/).
Manuel Hiebel 2012-12-13 00:58:56 CET

CC: (none) => fundawang

Comment 1 Florian Hubold 2014-11-01 00:05:42 CET
closing as old, problem doesn't exist anymore.

ââââ¼ LC_ALL=C sudo urpmi evolution-sharp
http://ftp.snt.utwente.nl/pub/os/linux/mageia/distrib/4/x86_64/media/core/release/evolution-sharp-0.21.1-18.mga4.x86_64.rpm
installing evolution-sharp-0.21.1-18.mga4.x86_64.rpm from /var/cache/urpmi/rpms                                                                                        
Preparing...                     #####################################################################################################################################
      1/1: evolution-sharp       #####################################################################################################################################

Status: NEW => RESOLVED
CC: (none) => doktor5000
Resolution: (none) => OLD


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