./build_package --fetchonly

[gerritbi...@gmail.com]

Hello,

Try to prepare a docker container that fetches everything during the build so I can use it as a backup to reproduce the OS when not connected to the Internet.
Repeatedly running in a problem with the fetchonly option. Is this specific for my setup or have more people this problem?

See below for details. Greetings Gerrit

[binary  N     ]   virtual/libudev-208:0/1::portage-stable to /build/amd64-usr/ USE="(-static-libs)" 0 KiB
[nomerge       ] sys-auth/polkit-0.113-r3::coreos to /build/amd64-usr/ USE="introspection pam systemd -examples -gtk -jit -kde -nls -selinux {-test}"

* Error: circular dependencies:

(sys-apps/systemd-229-r108:0/2::coreos, ebuild scheduled for merge to '/build/amd64-usr/') depends on
 (sys-apps/util-linux-2.27.1:0/0::portage-stable, binary scheduled for merge to '/build/amd64-usr/') (buildtime_slot_op)
  (sys-apps/systemd-229-r108:0/2::coreos, ebuild scheduled for merge to '/build/amd64-usr/') (runtime)

 * Note that circular dependencies can often be avoided by temporarily
 * disabling USE flags that trigger optional dependencies.

!!! The following binary packages have been ignored due to non matching USE:

    =sys-apps/systemd-229-r108 cryptsetup # for /build/amd64-usr/

NOTE: The --binpkg-respect-use=n option will prevent emerge
      from ignoring these binary packages if possible.
      Using --binpkg-respect-use=y will silence this warning.
[binary  N     ]  sys-auth/pambase-20120417-r6::coreos to /build/amd64-usr/ USE="sha512 systemd (-consolekit) -cracklib -debug -gnome-keyring -minimal -mktemp -pam_krb5 -pam_ssh -passwdqc -selinux" 0 KiB
[ebuild  N     ]   sys-apps/systemd-229-r108:0/2::coreos to /build/amd64-usr/ USE="audit curl gcrypt http importd kmod lzma nat pam policykit seccomp selinux symlink-usr (sysv-utils) (vanilla) -acl (-apparmor) -cryptsetup -elfutils -gnuefi -idn (-kdbus) -lz4 -man -profiling -qrcode (-ssl) {-test} -xkb" 0 KiB

Total: 14 packages (14 new, 13 binaries), Size of downloads: 5722 KiB
Running ['/home/coreos/src/scripts/sdk_lib/enter_chroot.sh', '--chroot', '/home/coreos/chroot', '--cache_dir', '/home/coreos/.cache', '--', './build_packages', '--fetchonly'] failed with exit code 1

[gerritbi...@gmail.com]

Hello,

Just an update. The problem is still reproducable. For anyone interested or willing to help, see https://github.com/INAETICS/build_coreos_sdk

Greetings Gerrit

[Michael Marineau]

When the build root is mostly empty (after ./setup_board but before
./build_packages) it isn't possible to build all packages from source
in one shot because of circular dependencies. To work around this
build_packages has some extra logic to incrementally install a few key
packages with different use flags. Alternatively the --usepkgonly can
be used to disable building from source. So the following should work:

# donwload/install baselayout and toolchain
./setup_board --force
# download binary packages
./build_packages --fetchonly --usepkgonly
# install binary packages
./build_packages --usepkgonly

At this point the build root will be fully installed but may be
slightly out of date compared to the current ebuild tree (the binary
packages will be from the latest alpha release) so build_packages can
be used to refresh:

# download source tarballs of outdated packages
./build_packagees --fetchonly
# compile/install updates
./build_packages

In general I don't really expect --fetchonly to be very useful right
now, it's been a very long time since I worked on making the SDK work
ok offline.