Description of problem:
hi there. it's been a few days since someone looked at another bug i posted--
but don't know what else to do w/ it. the person who took the report didn't
really say what i was supposed to do... and by now, i wonder, was that the end
of the transaction on the other report? 

the problem lies in a continued request for libsyck.so.0 which result in an
inability to proceed w/ updating the system.
i don't even know what it is a component of -- i thought yum was the problem,
considering it was YumEx which sugested i submit a bug report, but someone over
there said it looked like a dependency issue-- and i didn't know how to proceed
w/ that. (i mean, i know what a dependency is-- but, i didn't know what other
info to provide)
obviously, i'm unable to find any info about libsyck.so.0 
the other report is here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208747
NOTE: if indicated what this component is related to-- perhaps i could find more
info to submit.

Version-Release number of selected component (if applicable):
Linux localhost.localdomain 2.6.17-1.2187_FC5 #1 Mon Sep 11 01:17:06 EDT 2006
i686 athlon i386 GNU/Linux


How reproducible:
try to update yum or yumex


Steps to Reproduce:
1. open yumex 
2. add all updates to queue
3. proceed w/ update
i documented every step of the process as a screen cap here:
http://fedorashare.centrewebdesign.com/rhbugzilla/ 
  
Actual results:
an error declaring the dependency

Expected results:
an update for the system via yum or yumex.

Additional info:
thank you!! i apologize for submitting the same issue twice-- but it's the first
i've submitted a report-- so i don't know what is supposed to happen.