-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
minikube: 1.0.1 -> 1.2.0 #65412
minikube: 1.0.1 -> 1.2.0 #65412
Conversation
@GrahamcOfBorg build minikube |
Sorry for hijacking this PR, this is not an issue with this PR itself, it's much larger. We're accepting more and more packages using I'd like us to stop accepting new packages that are abusing FODs and start working on gradually removing these abuses. |
I don't know enough about the particular builder but it seems like |
Thanks for the pointer, I have missed this issue. I don't think we should worry about that now. It's an issue today, and won't be resolved for a long while. Until then, we should do business as usual. Whatever the solution will be, it will have to take into account the current packages by either changing |
@GrahamcOfBorg build minikube |
Also switch to go modules. Signed-off-by: Vincent Demeester <vincent@sbr.pm>
25dc7c5
to
a12efe9
Compare
@adisbladis I do not see this being the case, there's a discussion how to solve this issue, but until better solution is found, we rather have a way to have packages updated, as to stop packaging. PS: and you can also see that many people disagree with proposed restrictions, as there are currently only bad alternatives |
@GrahamcOfBorg build minikube |
Darwin failure is unrelated, seems like clang is failing |
Motivation for this change
Bump to latest release (1.2.0) and switch to go modules.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)