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

tuxedo-keyboard: 3.0.7 -> 3.0.8 #136108

Merged
merged 2 commits into from
Aug 29, 2021
Merged

tuxedo-keyboard: 3.0.7 -> 3.0.8 #136108

merged 2 commits into from
Aug 29, 2021

Conversation

blitz
Copy link
Contributor

@blitz blitz commented Aug 29, 2021

Motivation for this change

This PR bumps the tuxedo-keyboard module to its latest version and exposes all kernel modules from it. tuxedo_io is required to run the Tuxedo Control Center.

Relates to #135841 and #132206.

Things done
  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • 21.11 Release Notes (or backporting 21.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.

This commit exposes in addition to the tuxedo-keyboard module:

- clevo_acpi
- clevo_wmi
- tuxedo_io

These modules are required to run the Tuxedo Control Center.
@blitz
Copy link
Contributor Author

blitz commented Aug 29, 2021

@Mic92 I've split out the kernel module update from #135841 to avoid blocking this on the TCC packaging issues.

@Mic92
Copy link
Member

Mic92 commented Aug 29, 2021

Should we backport this?

@blitz
Copy link
Contributor Author

blitz commented Aug 29, 2021

Should we backport this?

Yes.

@github-actions
Copy link
Contributor

Backport failed for release-21.05, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally.

git fetch origin release-21.05
git worktree add -d .worktree/backport-136108-to-release-21.05 origin/release-21.05
cd .worktree/backport-136108-to-release-21.05
git checkout -b backport-136108-to-release-21.05
ancref=$(git merge-base 6b369a4de7e6b5ed7d4519581de3bc3d7a3cd5be 2e6d563067c620d42c9d63911a637793698273eb)
git cherry-pick -x $ancref..2e6d563067c620d42c9d63911a637793698273eb

@blitz
Copy link
Contributor Author

blitz commented Aug 29, 2021

@Mic92 There is one commit missing to auto-backport. I'll manually open a PR.

@blitz blitz changed the title tuxedo-keyboard: 1.0.7 -> 1.0.8 tuxedo-keyboard: 3.0.7 -> 3.0.8 Aug 30, 2021
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