Problems with the New GraphicsMagick in Unstable

[Gene Smith]

Rex Dieter wrote, On 09/26/2009 07:46 AM:
> On 09/26/2009 06:13 AM, Eli Wapniarski wrote:
>> Hi
>>
>>
>> I get the following problems with the newer package in the Unstable repository
>>
>> on my i386 machine
>> ---------------------
>> dvdauthor-0.6.14-8.fc11.i586 from installed has depsolving problems
>>    -->  Missing Dependency: libGraphicsMagick.so.1 is needed by package dvdauthor-0.6.14-8.fc11.i586 (installed)
>>
>> Also, the same thing happened on x86_64 desktop plus k9copy was affected by the same problem
>
> https://admin.fedoraproject.org/updates/F11/FEDORA-2009-9839
>
> -- Rex

Been having the same problem with updating GraphicsMagick in relation to 
koffice-krita for over a week I think. Can you tell what my problem is? 
Not sure what the link you refer to above is suppose to indicate w.r.t. 
this problem.

Here's what I see with yum update:

sudo yum update koffice* GraphicsMagick
Loaded plugins: fastestmirror, refresh-packagekit
Loading mirror speeds from cached hostfile
  * fedora: ftp.us.unixeria.com
  * livna: rpm.livna.org
  * rpmfusion-free: mirrors.tummy.com
  * rpmfusion-free-updates: mirrors.tummy.com
  * rpmfusion-nonfree: mirrors.tummy.com
  * rpmfusion-nonfree-updates: mirrors.tummy.com
  * rtems-4.9: www.rtems.org
  * updates: ftp.us.unixeria.com
  * updates-testing: ftp.us.unixeria.com
Setting up Update Process
Resolving Dependencies
--> Running transaction check
--> Processing Dependency: libGraphicsMagick.so.1()(64bit) for package: 
2:koffice-krita-2.0.1-2.fc11.x86_64
---> Package GraphicsMagick.x86_64 0:1.3.7-1.fc11 set to be updated
--> Finished Dependency Resolution
2:koffice-krita-2.0.1-2.fc11.x86_64 from installed has depsolving problems
   --> Missing Dependency: libGraphicsMagick.so.1()(64bit) is needed by 
package 2:koffice-krita-2.0.1-2.fc11.x86_64 (installed)
Error: Missing Dependency: libGraphicsMagick.so.1()(64bit) is needed by 
package 2:koffice-krita-2.0.1-2.fc11.x86_64 (installed)
  You could try using --skip-broken to work around the problem
  You could try running: package-cleanup --problems
                         package-cleanup --dupes
                         rpm -Va --nofiles --nodigest