On Tue, Mar 14, 2017 at 2:03 PM, 'Matt Mathis' via CoreOS Dev <[email protected]> wrote: >> (sys-fs/cryptsetup-1.7.2:0/0::portage-stable, ebuild scheduled for merge >> to '/build/amd64-usr/') depends on >> (sys-fs/lvm2-2.02.145-r3:0/0::coreos, ebuild scheduled for merge to >> '/build/amd64-usr/') (buildtime) >> (sys-apps/systemd-231-r12:0/2::coreos, binary scheduled for merge to >> '/build/amd64-usr/') (buildtime_slot_op) >> (sys-fs/cryptsetup-1.7.2:0/0::portage-stable, ebuild scheduled for >> merge to '/build/amd64-usr/') (runtime_slot_op) >> It might be possible to break this cycle >> by applying the following change: >> - sys-fs/lvm2-2.02.145-r3 (Change USE: -systemd).
The master branch should work, but you have to disable binary packages to avoid this issue until the next alpha release (Thursday) uploads its own binary packages. Try "./build_packages --nousepkg" until then. > One last thing, I am under the impression that the precise errors have > changed over the last few days. Is somebody currently reworking the > dependencies? Is there a way to pin my work to a stable version? There should be no problem with the build-1339 branch, since that was released before the changes resulting in the above binary package failures. If it is still failing for you, try starting on that branch with a fresh SDK in case there are now conflicting binary packages cached on your system. Thanks. David
