On Fri, 03 Apr 2015 17:29:30 +0200, Axel Beckert wrote: > I've tried to have a look into the issue and started with trying to > reproduce it. But I fail to even create a base.qemu with it: > > # qemubuilder --create > forking: mke2fs -q -F -j -m1 -O sparse_super /var/cache/pbuilder/base.qemu > forking: tune2fs -c 0 -i 0 /var/cache/pbuilder/base.qemu > tune2fs 1.42.12 (29-Aug-2014) > Setting maximal mount count to -1 > Setting interval between checks to 0 seconds > forking: mount -o loop /var/cache/pbuilder/base.qemu > /var/cache/pbuilder/build//qemu.4106 > mount: /var/cache/pbuilder/build//qemu.4106: mount failed: Unknown error -1 > # > > I haven't found out yet what exactly caused that "Unknown error", but > the error message clearly comes from the mount command. There's no > hint in the dmesg output either (although I found a qemubuilder > segfault in there, but that seemed earlier and is not reproducible).
I get a bit further: # qemubuilder --create --distribution sid --architecture armel --basepath /var/cache/pbuilder/base-test.qemu forking: mke2fs -q -F -j -m1 -O sparse_super /var/cache/pbuilder/base-test.qemu forking: tune2fs -c 0 -i 0 /var/cache/pbuilder/base-test.qemu tune2fs 1.42.12 (29-Aug-2014) Setting maximal mount count to -1 Setting interval between checks to 0 seconds forking: mount -o loop /var/cache/pbuilder/base-test.qemu /var/cache/pbuilder/build//qemu.19020 -> Invoking debootstrap forking: debootstrap --arch armel --foreign sid /var/cache/pbuilder/build//qemu.19020 http://ftp.ch.debian.org/debian I: Retrieving Release I: Retrieving Release.gpg I: Checking Release signature I: Valid Release signature (key id A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553) I: Retrieving Packages I: Validating Packages [.. package downloads ..] I: Extracting zlib1g... -> Doing architecture-specific /dev population mkdir chroot-/dev: File exists forking: umount /var/cache/pbuilder/build//qemu.19020 forking: mke2fs -q -F -j -m1 -O sparse_super /var/cache/pbuilder/build//qemu.19020.dev forking: tune2fs -c 0 -i 0 /var/cache/pbuilder/build//qemu.19020.dev tune2fs 1.42.12 (29-Aug-2014) Setting maximal mount count to -1 Setting interval between checks to 0 seconds forking: mount -o loop /var/cache/pbuilder/build//qemu.19020.dev /var/cache/pbuilder/build//qemu.19020 forking: umount /var/cache/pbuilder/build//qemu.19020 but here it hangs forever and I also have a qemubuilder segfault. > > This bug is currently marking cowdancer for automatic removal from > > Jessie. > I'll try to have another look at these two issues later today. But if > I don't find a fix to both, I suggest to upload a cowbuilder source > package with the qemubuilder binary package not being build for Jessie > and re-adding it (hopefully with these issues fixed properly) after > the Jessie release. That's one option I also thought about. The other would obviously be a jessie-ignore tag by the RT. In any way, having no cowbuilder because of a broken qemubuilder doesn't sounds like a good option :) /* A more general question is if qemubuilder is really needed. Crosscompiling works with cowbuilder/pbuiler and qemu-debootstrap as well: http://info.comodo.priv.at/blog/cowbuilder_crossbuilds_for_raspbian.html */ Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Andrew Lloyd Webber & Tim Rice
signature.asc
Description: Digital Signature
