On Wednesday, June 14, 2017 11:52:35 AM CEST Michal Novotny wrote:
Actually, this is a bug. systemd-nspawn "chroots" are now
used for building
and there is a different config option for network-enabling them. Now it's
rpmbuild_networking, before it was use_host_resolv.
I would suggest to define both use_host_resolv and rpmbuild_networking options
based on Copr's "Enable Networking" checkbox... just for the cases that
some of
the copr deployments decided to not move to systemd_nspawn that quickly.
Perhaps the systemd_nspawn itself could be 'opt-out', too?
Pavel