Description of Problem: A core file (from a very big machine ;o) has been inadvertently included in the latest linuxdoc-tools build. This causes the install to fail on my machine (I dare say there are those who didn't notice ;o) Version-Release number of selected component (if applicable): linuxdoc-tools-0.9.16 How Reproducible: Try to install the package. Actual Results: [root@pikachu tmp]# rpm -Uvh linuxdoc-tools-0.9.16-1.i386.rpm Preparing... ########################################### [100%] 1:linuxdoc-tools error: unpacking of archive failed on file /usr/share/doc/linuxdoc-tools-0.9.16/core;3c574ea8: cpio: write failed - No space left on device Expected Results: [root@pikachu tmp]# rpm -Uvh --excludepath /usr/share/doc/linuxdoc-tools-0.9.16/core linuxdoc-tools-0.9.16-1.i386.rpm Preparing... ########################################### [100%] 1:linuxdoc-tools ########################################### [100%]
That's not good. I'll take a look.
Couldn't reproduce it. Rebuilding the package made the problem go away. Perhaps it was a perl problem that's now been fixed or something. *shrug*
*shrug* *grin* I figured the same. Just thought you should know, in case noone else reported it (I suspected that most of you probably have enough disk space to miss this ;o)
Indeed, there is a perl problem of some kind... My XFree86 builds are also failing on stripples randomly. It is _always_ perl which is segv'ing randomly. Just thought I'd add that datapoint for anyone querying the database.
Changing component, reopening.
Reassigning.
Something similar just happened while building the cups-drivers package (also on stripples) - foomatic-datafile (a perl script) went up to using 99.9% CPU time and simply hung. Also not reproducable outside the build system.
Closing due to lack of activity.