| Summary: | sys-cluster/minikube-1.6.2 fails to emerge when `network-sandbox` feature is enabled | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Loty Gero <lotgyero> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | lotgyero, lssndrbarbieri, williamh |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Loty Gero
2020-03-09 21:15:29 UTC
Same with dnscrypt-proxy Also happens with: app-admin/helm app-emulation/libpod 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 All, this should be fixed. please sync again and verify. Thanks, William I have been advised that minikube builds successfully now. Thanks, William |