Bug 843911

Summary:	ImageMagick cannot be installed anymore
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Manfred Hollstein <manfred.h>
Component:	Upgrade Problems	Assignee:	Petr Gajdos <pgajdos>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	manfred.h
Version:	13.1 Beta 1
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Manfred Hollstein 2013-10-03 15:28:30 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0

This happened during an upgrade from openSUSE-13.1 Milestone4 to openSUSE-13.1 Beta1:

# zypper dup
...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Loading repository data...
Reading installed packages...
Computing distribution upgrade...

The following NEW package is going to be installed:
  ImageMagick 

1 new package to install.
Overall download size: 4.0 MiB. After the operation, additional 8.6 MiB will be used.
Continue? [y/n/?] (y): 
(1/1) Installing: ImageMagick-6.8.6.9-2.3.4 ............................................[error]
Installation of ImageMagick-6.8.6.9-2.3.4 failed:
Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/share/doc/packages/ImageMagick/www/api/MagickCore/exception_8h.html;524d8b46: cpio: link
error: ImageMagick-6.8.6.9-2.3.4.x86_64: install failed


Abort, retry, ignore? [a/r/i] (a): a
Problem occured during or after installation or removal of packages:
Installation aborted by user

Please see the above error message for a hint.


Reproducible: Always

Steps to Reproduce:
1. rpm -e ImageMagick
2. zypper in ImageMagick
3. or: zypper dup

Comment 1 Petr Gajdos 2013-10-04 07:15:43 UTC

Should be fixed yet. Nevertheless thanks for reporting!

*** This bug has been marked as a duplicate of bug 841472 ***