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
tailscale: init at 0.97-0 [20.03 backport] #82827
Conversation
cc 20.03 RMs: @worldofpeace @disassembler |
I can't remember if we had some knowledge on restricting backports of new modules. |
pkgs/servers/tailscale/default.nix
Outdated
version = "v0.97"; | ||
|
||
src = fetchFromGitHub { | ||
owner = "tailscale"; | ||
repo = "tailscale"; | ||
rev = "v0.97"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
version = "v0.97"; | |
src = fetchFromGitHub { | |
owner = "tailscale"; | |
repo = "tailscale"; | |
rev = "v0.97"; | |
version = "0.97"; | |
src = fetchFromGitHub { | |
owner = "tailscale"; | |
repo = "tailscale"; | |
rev = "v${version}"; |
nixpkgs manual says version shouldn't have that character in it.
Not sure if this commit is on master yet or not?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Woops, adding your suggested change resolved this.
To your other question: the version adjust isn't in master yet. I'll queue up a PR to do that as well. The version+rev change is a no-op on the built binaries though, since the v0.97 tag references the commit hash we used in the initial commit to unstable.
I don't really see any reason to prevent this from a technical standpoint, though I would have liked to see more info about the project in the OP, had to iron those details out on IRC. |
So I don't really get fixing the version here and then I guess forward porting to master. I guess canonically you should have that commit in master and then backport it. |
Ack. I'll send a PR to master, then adjust this PR to be purely cherry-picks from master. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving like I did on IRC.
Signed-off-by: Martin Baillie <martin@baillie.email> (cherry picked from commit 6e055c9)
Fixes a severe bug with subnet routing. Signed-off-by: David Anderson <dave@natulte.net> (cherry picked from commit f61f686)
The tag points to the same commit hash, so the binary is unchanged. Signed-off-by: David Anderson <dave@natulte.net> (cherry picked from commit 3fa813e)
9ca7119
to
752d976
Compare
Updated to only contain cherry-picks from master. |
Motivation for this change
New package+module, just landed in master. The package and module are both leaves, nothing depends on them, so it should be very safe to add.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)