I am working a script that follows https://coreos.com/os/docs/latest/sdk-modifying-coreos.html, but it has stopped working recently with "circular dependencies" errors.
The sequence: repo init -u https://github.com/coreos/manifest.git -b master (... sync ... cros_sdk --download ... cros_sdk --create ...) ./chromite/bin/cros_sdk --enter -- ./setup_board --default --board=amd64-usr ./chromite/bin/cros_sdk --enter -- ./build_packages Gets errors: > (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). In another (old) thread, it was suggested to the do the build_packages in phases: ./chromite/bin/cros_sdk --enter -- ./build_packages --fetchonly --usepkgonly ./chromite/bin/cros_sdk --enter -- ./build_packages --usepkgonly ./chromite/bin/cros_sdk --enter -- ./build_packages --fetchonly ./chromite/bin/cros_sdk --enter -- ./build_packages But all of these fail with similar but slightly different circular dependency errors. (BTW all of my changes have been bypassed.) I have also tried CoreOS manifest branch build-1339. 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?
