lib64/systemd/systemd-vconsole-setup lib64/systemd/user-generators make: *** [stage1/usr_from_coreos/build-usr.mk:162: /var/tmp/portage/app-emulation/rkt-1.26.0/work/rkt-1.26.0/build-rkt-1.26.0/stamps/__stage1_usr_from_coreos_build_usr_mkfor_usr_from_coreos_mk_mkbase.stamp] Error 1 * ERROR: app-emulation/rkt-1.26.0::gentoo failed (compile phase): * emake failed * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: plasma-systemd_libressl_20170609-232249 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.3.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback)
Created attachment 477390 [details] emerge-info.txt
Created attachment 477392 [details] app-emulation:rkt-1.26.0:20170620-094842.log
Created attachment 477394 [details] emerge-history.txt
Created attachment 477396 [details] environment
Created attachment 477398 [details] etc.portage.tbz2
Created attachment 477400 [details] logs.tbz2
Created attachment 477402 [details] temp.tbz2
Seems to be failing right here: https://github.com/rkt/rkt/blob/v1.26.0/stage1/usr_from_coreos/build-usr.mk#L170 It's calling unsquashfs. What version of squashfs-tools do you have?
(In reply to Zac Medico from comment #8) Mon Jun 12 06:27:34 2017 >>> sys-fs/squashfs-tools-4.3-r2
It works for me with sys-fs/squashfs-tools-4.3-r2. Is the problem reproducible?
(In reply to Zac Medico from comment #10) at that particular image : yes, it isntalls fine eg at 17.0-desktop-gnome-libressl_20170611-103213
Masked for removal: bug 687100
