RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1024985 - error: error unpacking of archive failed with spice-server-0.12.0-12.el6_4.5.x86_64
Summary: error: error unpacking of archive failed with spice-server-0.12.0-12.el6_4.5....
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-server
Version: 6.4
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Default Assignee for SPICE Bugs
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-30 17:21 UTC by Kay Williams
Modified: 2014-05-02 11:52 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-22 00:26:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Kay Williams 2013-10-30 17:21:19 UTC
Description of problem:
With the latest release of spice-server. an error occurs installing or updating the package. The complete error is:

Error unpacking of archive failed on file /usr/lib64/libspice-server.so.1.5.0;xxxxxxxx: cpio: read failed - resource temporarily unavailable

In the test environment, the package is being installed/updated to a libvirt based virtual machine. No testing has been done on a physical machine.

Version-Release number of selected component (if applicable):
spice-server-0.12.0-12.el6_4.5.x86_64.rpm

How reproducible:
Always

Steps to Reproduce:
1a. Install a clean system using virt-install. Specify only the core group and spice-server package.
1b. Anaconda fails during installation of the spice-server package.

2a. On an existing virtual machine (created using virt-install). Attempt to perform yum update
2b. Yum fails during update of spice server package.

Comment 2 RHEL Program Management 2013-11-02 18:44:54 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 Marc-Andre Lureau 2014-02-21 15:42:50 UTC
From
https://brewweb.devel.redhat.com/buildinfo?buildID=299892

rpm2cpio spice-server-0.12.0-12.el6_4.5.x86_64.rpm  | cpio -idmv

works fine, could you check the checksum/digest is same?

Could you give more precise instructions of what iso you downloaded or which yum repo etc? thanks

Comment 4 Kay Williams 2014-02-22 00:11:59 UTC
Thank you for following up. I am no longer seeing this issue with current versions of spice-server, specifically spice-server-0.12.4-6.el6_5.1.x86_64. Please feel free to close.


Note You need to log in before you can comment on or make changes to this bug.