I've updated my laptop this morning with the last kernel-stable 3.13.7 available.
Since then build package with osc build create a new kind of error never seen before
I'm using a -virtio initrd and build in kvm mode.
[ 28s] libgtk-2_0-0-2.24.22-2.1 ######################################## [ 28s] error: unpacking of archive failed on file /usr/lib64/libgtk-x11-2.0.so.0.2400.22;533830a1: cpio: read failed - Inappropriate ioctl for device [ 28s] error: libgtk-2_0-0-2.24.22-2.1.x86_64: install failed
The error appear at random package, I've tried to build different package same result.
I'm using the whole stack of repo:virtualization ( thus I've no idea if its correlated )
But having the laptop on with 3.13.7 and running the build with 3.11.10 work normally.
What is the best way to report that as a bug, and against which component.
Bruno Friedmann bruno@ioda-net.ch writes:
[ 28s] error: unpacking of archive failed on file /usr/lib64/libgtk-x11-2.0.so.0.2400.22;533830a1: cpio: read failed - Inappropriate ioctl for device
The actual error message is a red herring, it's a bug in rpm that the real errno is lost on the way.
(ENOTTY is the error reported by isatty(3).)
Andreas.
On Sunday 30 March 2014 17.50:33 Andreas Schwab wrote:
Bruno Friedmann bruno@ioda-net.ch writes:
[ 28s] error: unpacking of archive failed on file /usr/lib64/libgtk-x11-2.0.so.0.2400.22;533830a1: cpio: read failed - Inappropriate ioctl for device
The actual error message is a red herring, it's a bug in rpm that the real errno is lost on the way.
(ENOTTY is the error reported by isatty(3).)
Andreas.
Andreas, anything I can try to dig and get more useful informations ?
First, you have to tell use more about your package. Without that information there is nothing that can be done to help you.
Andreas.
On Monday 31 March 2014 10.58:39 Andreas Schwab wrote:
First, you have to tell use more about your package. Without that information there is nothing that can be done to help you.
Andreas.
For example with standard 3.11.10 kernel for 13.1 I could compile locally https://build.opensuse.org/package/show/home:bruno_friedmann:mapserver6/maps... or newer version like https://build.opensuse.org/package/show/home:bruno_friedmann:mapserver64/map...
without any trouble ( as obs can ) I've sucess build 100% of time.
Now using 3.13.7 (inside the kvm buildroot)
I've build one time the mapserver64 and following try failed [ 36s] chrpath-0.13-154.1.2 ######################################## [ 36s] exit ... [ 40s] [ 32.215555] SysRq : Power Off [ 40s] [ 32.216840] reboot: Power down
or at different location & time build for the 6.0
[ 55s] collect2: error: ld terminated with signal 11 [Segmentation fault] [ 55s] make: *** [shptreetst] Error 1 [ 55s] make: *** Waiting for unfinished jobs.... [ 55s] collect2: error: ld terminated with signal 11 [Segmentation fault] [ 55s] make: *** [shptreevis] Error 1 [ 56s] error: Bad exit status from /var/tmp/rpm-tmp.QrAijZ (%build)
All build are run like this
[ 4s] booting kvm ... [ 4s] /usr/bin/qemu-kvm -no-reboot -nographic -vga none -net none -cpu host -kernel /boot/vmlinuz -initrd /boot/initrd-3.13.7-1.ga68bc7c-desktop-virtio -append root=/dev/vda panic=1 quiet no-kvmclock nmi_watchdog=0 rw elevator=noop console=ttyS0 init=/.build/build -m 4096 -drive file=/dev/mapper/vg0-lvobsbuild,if=virtio,cache=none -drive file=/dev/mapper/vg0-lvobsbuild,if=ide,index=0,cache=none -drive file=/dev/mapper/vg1-lvobsswap,if=virtio,cache=none -smp 8 [ 9s] WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. [ 9s] Volume group "vg0" not found [ 9s] WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. [ 9s] Volume group "vg0" not found [ 9s] ./run_all.sh: line 108: source: boot/: is a directory [ 9s] Trying manual resume from /dev/vg0/lvswap [ 9s] resume device /dev/vg0/lvswap not found (ignoring) [ 9s] Trying manual resume from /dev/vg0/lvswap [ 9s] resume device /dev/vg0/lvswap not found (ignoring) [ 9s] Waiting for device /dev/vda to appear: ok [ 9s] fsck from util-linux 2.23.2 [ 9s] [/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/vda [ 9s] /dev/vda: clean, 3628/786432 files, 114195/3145728 blocks [ 9s] fsck succeeded. Mounting root device read-write. [ 9s] Mounting root /dev/vda [ 9s] mount -o rw -t ext4 /dev/vda /root
The build work sometimes but at a 30% average 3 times successful on a 10 times run.
It was not the case with 3.13.6 :-(
What can I do to give you more useful information ?