Hi, I'm maintainer of Flatcar Linux <https://flatcar-linux.org>. I'm aware that it's coreos-dev list. Though since Flatcar Linux is a fork of Container Linux, I'm pretty sure some of you could have some idea about my issue.
Recently I started seeing strange build issues since v1967.0.0. A typical error happens during builds of Flatcar SDK like below: >>> Emerging (1 of 1) sys-apps/portage-2.3.40-r1::coreos >>> Installing (1 of 1) sys-apps/portage-2.3.40-r1::coreos Updating seed stage... emerge --quiet --update --deep --newuse --complete-graph --rebuild-if-new-ver gcc emerge: there are no ebuilds to satisfy "dev-util/cargo:0". I suppose, it started to occur since the PR https://github.com/coreos/coreos-overlay/pull/3458 was merged. The description looks fine. Since there's no need to keep coreos-cargo any more, all rust-related packages were moved to portage-stable instead. That makes a perfect sense. Following the principle, I made both coreos-overlay and portage-stable in sync with upstream coreos repos. Nevertheless I'm still seeing the ebuilds error during SDK builds. Does anyone have an idea, how I can fix (or workaround) the issue? Thanks, Dongsu
