affected with 1.7.0/1.8.0 also Reproducible: Always
Created attachment 629256 [details] build.log.tar.xz
Created attachment 629258 [details] emerge-info
What version of dev-lang/go do you have? I didn't see this issue with dev-lang/go-1.14.
Not the reporter but I run into the same issue with 1.13.9 (stable).
Same here one three different systems with go 1.13.9
(In reply to Zac Medico from comment #3) > What version of dev-lang/go do you have? I didn't see this issue with > dev-lang/go-1.14. Are you sure that it will work with another version of go? The portage sandbox should not allow network access. The dependencies should be fetched and packaged. https://forums.gentoo.org/viewtopic-t-1102468-start-0.html i added "-network-sandbox" in make.conf FEATURES= and i can emerge. Would be great if libpod would emerge without this anti-feature.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3df896d7f88c8d3c97723ac9c022c26957098c4b commit 3df896d7f88c8d3c97723ac9c022c26957098c4b Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2020-04-05 19:39:38 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2020-04-05 19:39:51 +0000 app-emulation/libpod: fix network-sandbox for go-1.13.9 Closes: https://bugs.gentoo.org/715980 Package-Manager: Portage-2.3.96, Repoman-2.3.22 Signed-off-by: Zac Medico <zmedico@gentoo.org> app-emulation/libpod/libpod-1.8.2.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)