Description of problem:
Latest released update appears to be compiled against old version of libpisock.
Version-Release number of selected component (if applicable):
Every update or install
Steps to Reproduce:
1.yum update or yum update evolution
# yum update
Setting up Update Process
Setting up repositories
Reading repository metadata in from local files
--> Populating transaction set with selected packages. Please wait.
---> Package netpbm-devel.i386 0:10.33-1.FC4 set to be updated
---> Package bind.i386 24:9.3.1-20.FC4 set to be updated
---> Package netpbm-progs.i386 0:10.33-1.FC4 set to be updated
---> Package wine.i386 0:0.9.11-2.fc4 set to be updated
---> Package gaim.i386 1:1.5.0-16.fc4 set to be updated
---> Package netpbm.i386 0:10.33-1.FC4 set to be updated
---> Package bind-utils.i386 24:9.3.1-20.FC4 set to be updated
---> Package selinux-policy-targeted.noarch 0:1.27.1-2.28 set to be updated
---> Package evolution.i386 0:2.2.3-4.fc4 set to be updated
---> Package bind-libs.i386 24:9.3.1-20.FC4 set to be updated
---> Package sane-backends.i386 0:1.0.17-0.fc4.2 set to be updated
---> Package pilot-link-devel.i386 1:0.12.0-0.pre4.0.fc4.2 set to be updated
--> Running transaction check
--> Processing Dependency: libpisock.so.8 for package: evolution
--> Finished Dependency Resolution
Error: Missing Dependency: libpisock.so.8 is needed by package evolution
Hunting around, it looks like pilot-link 0.11.8 was never included in FC4, only
FC3. Rolling back to 2.2.3-2 works fine with pilot-link-0.12.0 and libpisock.so.9.
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
The distribution against which this bug was reported is no longer supported,
could you please reproduce this with the updated version of the currently
supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue
turns out to still be reproducible, please let us know in this bug report. If
after a month's time we have not heard back from you, we will have to close this
bug as INSUFFICIENT_DATA.
Setting status to NEEDINFO, and awaiting information from the reporter.
Thanks in advance.
Closing as INSUFFICIENT_DATA.