Skip to content
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

[24.11] headscale: backport BaseDomain and ServerURL checks #357969

Open
wants to merge 1 commit into
base: release-24.11
Choose a base branch
from

Conversation

motiejus
Copy link
Contributor

@motiejus motiejus commented Nov 21, 2024

Currently users upgrading from 24.05 to 24.11 may stumble across an overly-restrictive BaseURL and ServerURL check in headscale1.

A fix has been merged upstream2, this is backport, so users can have it easier upgrading from 24.05 to 24.11.

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

Currently users upgrading from 24.05 to 24.11 may stumble across an
overly-restrictive BaseURL and ServerURL check in headscale[1].

A fix has been merged upstream[2], this is backport, so users can have
it easier upgrading from 24.05 to 24.11.

[1]: juanfont/headscale#2210
[2]: juanfont/headscale#2248
@06kellyjac
Copy link
Member

Since this is merged upstream can we fetchpatch the upstream commit please. Plus a comment to remove next release.

Also could you make the PR against master and we can backport to 24.11 from there.

@motiejus
Copy link
Contributor Author

Since this is merged upstream can we fetchpatch the upstream commit please. Plus a comment to remove next release.

This does not apply cleanly to the released version, thus the patch.

Also could you make the PR against master and we can backport to 24.11 from there.

Ok.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants