Bug 712750 - error: unpacking of archive failed on file /lib/lib/nspr4.so;4df4f495: cpio: read failed - Resource temporarily unavailable
Summary: error: unpacking of archive failed on file /lib/lib/nspr4.so;4df4f495: cpio: ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 15
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Panu Matilainen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-13 01:17 UTC by Klaus Pedersen
Modified: 2012-08-07 18:05 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 18:05:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Klaus Pedersen 2011-06-13 01:17:54 UTC
Description of problem:

(pre-)upgrading of F-14 to F-15 fails when unpacking nspr.
There seems to be some noise in filename.

Version-Release number of selected component (if applicable):
 * nspr-4.8.8-1.fc15.i686

How reproducible:
 * 100%

Steps to Reproduce:
1. Perform a preupgrade from F-14 to F-15


Actual results:

Anaconda:

"[-] Error Installing Package "
" A fatal error occurred when installing nspr "
" package. .... "
" Installation cannot continue "
"       [ Exit Installer ] "


From /mnt/sysimage/root/install.log ...

...
Upgrading nspr-4.8.8-1.fc15.i686
error: unpacking of archive failed on file /lib/lib/nspr4.so;4df4f495: cpio: read failed - Resource temporarily unavailable


Expected results:

The upgrade should not fail(!)


Additional info:

This error looks similar to: https://bugzilla.redhat.com/show_bug.cgi?id=693394

There are no other exceptionally things in the logs - except an totally unrelated issue of overly verbose chatter from a very insistent dbus-daemon / ModemManager. There are 100's of messages like:

"NOTICE dbus-daemon: [system] Activating service 'org.freedesktop.ModemManager' failed Cannot lanuch daemon..."

(Why ModemManager is needed at this point is beyond me...)

Comment 1 Ondrej Vasik 2011-06-13 05:35:38 UTC
It is not similar - #693394 failed because the directory was not present (and that was the issue caused by systemd changes in filesystem package), this one seems to be different ... I don't think this is issue in filesystem package, I'll go with nspr as the starting point.

Comment 2 Klaus Pedersen 2011-06-13 06:16:23 UTC
(In reply to comment #1)
> It is not similar - #693394 failed because the directory was not present (and
> [...]

The two errors look similar in the sense that the symptoms are the same.

But you are right it is not the same root cause.
- I just figured that the problem is that a lot of packages was truncated:

[yum]# ls preupgrade-updates/packages/ -So | tail -14

-rw-r--r--. 2 root    10732 May 25 05:18 adwaita-gtk2-th[...]-1.fc15.i686.rpm
-rw-r--r--. 2 root     7380 Jun 12 15:24 gcc-4.6.0-9.fc15.i686.rpm
-rw-r--r--. 2 root     7380 Jun 12 15:24 gcc-c++-4.6.0-9.fc15.i686.rpm
-rw-r--r--. 2 root     7380 Jun 12 15:24 gcc-gfortran-4.6.0-9.fc15.i686.rpm
-rw-r--r--. 2 root     7380 Jun 12 15:24 gcc-java-4.6.0-9.fc15.i686.rpm
-rw-r--r--. 2 root     7380 Jun 12 15:24 gdb-7.2.90.20110525-38.fc15.i686.rpm
-rw-r--r--. 2 root     7380 Jun 12 15:24 gdm-3.0.4-1.fc15.i686.rpm
-rw-r--r--. 2 root     7380 Jun 12 15:24 gdm-plugin-fingerpri[...]c15.i686.rpm
-rw-r--r--. 2 root     7380 Jun 12 15:24 gedit-3.0.2-2.fc15.i686.rpm
-rw-r--r--. 2 root     7380 Jun 12 15:24 gedit-plugins-3.0.2-2.fc15.i686.rpm
-rw-r--r--. 2 root        0 Jun 12 15:48 gnome-devel-doc[...]1.fc15.noarch.rpm
-rw-r--r--. 2 root        0 Jun 12 16:23 imsettings-1.2.3-1.fc15.i686.rpm
-rw-r--r--. 2 root        0 Jun 12 16:52 kernel-headers-[...]-30.fc15.i686.rpm
-rw-r--r--. 2 root        0 Jun 12 19:08 nspr-devel-4.8.8-1.fc15.i686.rpm


So I assume the but is related to the preupgrade - i the sense it didn't
catch the error before suggesting to upgrade the system - or a better error
message.

I can't find any indication of why the files should be truncated.

Comment 3 Klaus Pedersen 2011-06-13 08:48:24 UTC
As concerned I am about preupgrade doen't notice/check that all the packages
are downloaded completely before barfing random noise when things go wrong.

I am even more puzzled about:

# rpmverify -p --nodeps  --nofiles preupgrade/gstreamer-pl[...].fc15.i686.rpm
warning: preupgrade/gstreamer-plugins-base-0.10.33-1.fc15.i686.rpm: Header V3 RSA/SHA256 Signature, key ID 069c8460: NOKEY

and then 

# rpm -Uvh preupgrade/gstreamer-plugins-base-0.10.33-1.fc15.i686.rpm 
warning: preupgrade/gstreamer-plugins-base-0.10.33-1.fc15.i686.rpm: Header V3 RSA/SHA256 Signature, key ID 069c8460: NOKEY
Preparing...                ########################################### [100%]
   1:gstreamer-plugins-base ########################################### [100%]
error: unpacking of archive failed on file /usr/lib/gstreamer-0.10/libgstsubparse.so;4df5ca7f: cpio: read failed - Bad file descriptor


So, rpmverify says "OK!" to the package, which is in fact broken!


Reminds me about: "If carpenters built buildings the way programmers write 
programs, then the first woodpecker to come along would destroy civilization"

Comment 4 Kamil Dudka 2011-06-20 13:43:18 UTC
Switching the component to rpm...

Comment 5 Fedora End Of Life 2012-08-07 18:05:17 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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