712008 – sys-cluster/minikube-1.6.2 fails to emerge when `network-sandbox` feature is enabled

Bug 712008 - sys-cluster/minikube-1.6.2 fails to emerge when `network-sandbox` feature is enabled

Summary: sys-cluster/minikube-1.6.2 fails to emerge when `network-sandbox` feature is ...

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal blocker (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2020-03-09 21:15 UTC by Loty Gero
Modified:	2020-03-10 18:45 UTC (History)
CC List:	3 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Loty Gero 2020-03-09 21:15:29 UTC

reproduce
dev-lang/go-1.12.15
dev-lang/go-1.13.8
dev-lang/go-1.14

Comment 1 Alessandro Barbieri 2020-03-10 09:34:09 UTC

Same with dnscrypt-proxy

Comment 2 Stijn Tintel 2020-03-10 13:44:09 UTC

Also happens with:

app-admin/helm
app-emulation/libpod

Comment 3 Stijn Tintel 2020-03-10 14:03:44 UTC

Reverting all commits to eclass/go-module.eclass one by one until 44b77ebef911630c5302b25bc708954738b35b56 fixed it, so I'm adding the author to CC.

Copying irc.freenode.net/gentoo:

10|14:53:03 <+iamben> stintel: the libpod failure seems to have been fixed w/ an ebuild change, i wonder if the new go changes jsut made it stricter on dep checks or something

Unfortunately that is not the case, app-emulation/libpod still fails after https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c979fbf04b85ccf20759a45aec6fbba94afc827a

Comment 4 William Hubbs gentoo-dev

2020-03-10 17:30:20 UTC

All,

this should be fixed. please sync again and verify.

Thanks,

William

Comment 5 William Hubbs gentoo-dev

2020-03-10 18:45:13 UTC

I have been advised that minikube builds successfully now.

Thanks,

William