Paul Meyer

Still an issue, and occurs quite often within the last month. Any update? We are still on github:cachix/cachix/3a6e4a049f7cadd8894015c2488a2fa969c83c41

I'm also co-organizer, hope we can boost the nix community in eastern Europe with this sprint! :)

@figsoda @Mic92 could I get a review on this and #640?

I have something like the following, where I want to ensure the hash is up to date after I updated foo (which is another package): ```nix { foo, fetchzip, }:...

> Ideally we should drop both? See https://discourse.nixos.org/t/why-do-so-many-go-packages-use-s-w-in-their-ldflags-it-breaks-dontfixup-dontstrip/36843. That's another topic and might require additional steps, see https://github.com/NixOS/nixpkgs/issues/346380.

Cool, thanks! Maybe we cav add a line to the help output to document the synopsis.

This is a problem as GitHub won't recognize the quoted version, so commits aren't liked to the authors profile.

Hey, I was facing the same problem with https://github.com/katexochen/gobuild.nix. There is a [patch on the Go toolchain in nixpkgs](https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/compilers/go/go_no_vendor_checks-1.22.patch) that introduced `GO_NO_VENDOR_CHECKS` env variable, which is [used by gomod2nix](https://github.com/nix-community/gomod2nix/blob/514283ec89c39ad0079ff2f3b1437404e4cba608/builder/default.nix#L267), too....

> Great, that sounds like the way to go! 👍 @obreitwi as I'm not used to gomod2nix, could you verify this solves the issue? Then I can merge the nixpkgs...

@zimbatm there is actually a workaround in place to prevent the rebuilds in another way (the comment pointed me to the problem in the first place): https://github.com/replit/upm/blob/91c21f5ca1ae1e664f9c288515e332517c385f6d/nix/upm/default.nix#L16-L20 This could be...