Realized at 3 different chroot images of the tinderbox that install hangs for hours : app-text/ttf2pt1-3.4.4-r1 @ amd64-13.0-unstable_20150903-153231 dev-util/bustle-0.5.1 @ amd64-gnome-unstable_20150913-104240 dev-util/cunit-2.1_p2-r1 @ amd64-desktop-unstable_20150915-205107 "emerge --debug" don't help here - any other info you need ? If I do manually log i into onbe of them and try it I get : # emerge --debug -1 app-text/ttf2pt1 myaction None myopts {'--tree': True, '--accept-properties': u'-interactive', '--accept-restrict': u'-fetch', '--nospinner': True, '--oneshot': True, '--debug': True, '--quiet-build': 'y', '--color': u'n'} myparams {'binpkg_changed_deps': 'auto', 'recurse': True, 'ignore_soname_deps': 'y', 'binpkg_respect_use': 'auto'} These are the packages that would be merged, in reverse order: Calculating dependencies .. Arg: app-text/ttf2pt1 Atom: app-text/ttf2pt1 ebuild: app-text/ttf2pt1-3.4.4-r1::gentoo ... forced rebuilds: >>> Verifying ebuild manifests >>> Emerging (1 of 1) app-text/ttf2pt1-3.4.4-r1::gentoo >>> Installing (1 of 1) app-text/ttf2pt1-3.4.4-r1::gentoo >>> Jobs: 0 of 1 complete Load avg: 10.4, 9.9, 8.9 and I have to kill -9 within another terminal then the emerge command. FWIW I portage are patched with https://gitweb.gentoo.org/proj/portage.git/commit/?id=024e2a5779e92fffbd0a0d30c8cff725c4552626 which shouldn't be the issu IMO.
Gah - all 3 images nearly started at the same time to show this issue and all 3 are located at a BTRFS volume - were the "good! images are running at a lvm device with ext4 - so rather an issue with BTRFS - I do just wonder what happened here.
kicked away BTRFS
