By default, Bugzilla does not search the list of RESOLVED bugs.You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
| Summary: |
Merged packages in fedora 19, bibletime fails to install |
| Product: |
TDE
|
Reporter: |
dacha1982 <danilo.bogdanov> |
| Component: |
fedora | Assignee: |
Timothy Pearson <kb9vqf> |
| Status: |
RESOLVED
FIXED
|
|
|
| Severity: |
normal
|
CC: |
albator78, bugwatch, danilo.bogdanov, michele.calgaro
|
| Priority: |
P5
|
|
|
| Version: |
3.5.13.2 [Trinity] | |
|
| Hardware: |
amd64 | |
|
| OS: |
Linux | |
|
|
Compiler Version:
|
|
TDE Version String:
|
|
|
Application Version:
|
|
Application Name:
|
|
Problem: on fedora 19, yum install -y trinity-desktop-all fails complaining about dependancies for bibletime package, which requires libsword, which is, I guess, now put in sword package. [root@radio ~]# yum -y install trinity-bibletime Loaded plugins: langpacks, refresh-packagekit google-chrome 3/3 Resolving Dependencies --> Running transaction check ---> Package trinity-bibletime.x86_64 0:1.6.6.0-6.fc19.opt will be installed --> Processing Dependency: sword for package: trinity-bibletime-1.6.6.0-6.fc19.opt.x86_64 --> Processing Dependency: libsword-1.6.2.so()(64bit) for package: trinity-bibletime-1.6.6.0-6.fc19.opt.x86_64 --> Running transaction check ---> Package sword.x86_64 0:1.7.2-1.fc19 will be installed ---> Package trinity-bibletime.x86_64 0:1.6.6.0-6.fc19.opt will be installed --> Processing Dependency: libsword-1.6.2.so()(64bit) for package: trinity-bibletime-1.6.6.0-6.fc19.opt.x86_64 --> Finished Dependency Resolution Error: Package: trinity-bibletime-1.6.6.0-6.fc19.opt.x86_64 (trinity-3.5.13) Requires: libsword-1.6.2.so()(64bit) Available: sword-1.6.2-10.fc19.x86_64 (fedora) libsword-1.6.2.so()(64bit) Installing: sword-1.7.2-1.fc19.x86_64 (updates) ~libsword-1.7.2.so()(64bit) You could try using --skip-broken to work around the problem Actually, this is bigger problem if someone tries to install virtual packages, like yum -y install trinity-desktop-all or yum -y install trinity-desktop-applications Workaround: first install sword: [root@radio ~]# yum -y install sword Then package directly with rpm -i and -nodeps: [root@radio ~]# rpm -i 'http://ftp.fau.de/trinity/trinity/rpm/f19/trinity-3.5.13/RPMS/x86_64/applications/trinity-bibletime-1.6.6.0-6.fc19.opt.x86_64.rpm' --nodeps [root@radio ~]# At this place, one can easily install trinity-desktop-all or trinity-desktop-applications with [root@radio ~]# yum -y install trinity-desktop-all Some tests I performed yum check complains [root@radio ~]# yum check Loaded plugins: langpacks, refresh-packagekit trinity-bibletime-1.6.6.0-6.fc19.opt.x86_64 has missing requires of libsword-1.6.2.so()(64bit) [root@radio ~]# ldd does not find library [root@radio ~]# ldd /opt/trinity/bin/bibletime | grep "not found" libsword-1.6.2.so => not found and linking with [root@radio ~]# ln -s /lib64/libsword-1.7.2.so /lib64/libsword-1.6.2.so ... does not solve problem [user@radio ~]$ bibletime bibletime: symbol lookup error: bibletime: undefined symbol: _ZN5sword6XMLTag7nullstrE (sometimes it is possible to link like this and to fix an issue, but I guess in this case 1.6.2 and 1.7.2 are not compatible ) But after all, trinity-desktop-all or trinity-desktop-applications will be installed without problems (at least related to bibletime)