Skip to content

Conversation

@l0b0
Copy link
Contributor

@l0b0l0b0 commented Dec 12, 2025

Closes#8161.

(cherry picked from commit 784a837)

Description

Checklist

  • Change is backwards compatible.

  • Code formatted with nix fmt or
    nix-shell -p treefmt nixfmt deadnix keep-sorted --run treefmt.

  • Code tested through nix run .#tests -- test-all or
    nix-shell --pure tests -A run.all.

  • Test cases updated/added. See example.

  • Commit messages are formatted like

    {component}:{description}{long description} 

    See CONTRIBUTING for more information and recent commit messages for examples.

  • If this PR adds a new module

    • Added myself as module maintainer. See example.
    • Generate a news entry. See News
    • Basic tests added. See Tests
  • If this PR adds an exciting new feature or contains a breaking change.

    • Generate a news entry. See News

@l0b0l0b0 changed the title release: mark as release branchnixos: Don't "[a]ttempt to evaluate package pkgs.trash-cli"Dec 12, 2025
@l0b0l0b0 changed the title nixos: Don't "[a]ttempt to evaluate package pkgs.trash-cli"nixos: Backport Don't "[a]ttempt to evaluate package pkgs.trash-cli"Dec 12, 2025
@l0b0l0b0 changed the title nixos: Backport Don't "[a]ttempt to evaluate package pkgs.trash-cli"nixos: Backport don't "[a]ttempt to evaluate package pkgs.trash-cli"Dec 12, 2025
@l0b0l0b0 changed the title nixos: Backport don't "[a]ttempt to evaluate package pkgs.trash-cli"nixos: Don't "[a]ttempt to evaluate package pkgs.trash-cli" [backport]Dec 12, 2025
@khaneliman
Copy link
Collaborator

In the future, just add the backport label for a PR you want to backport

@khanelimankhaneliman merged commit 90b6209 into nix-community:release-25.11Dec 13, 2025
7 checks passed
@l0b0l0b0 deleted the backport-8242 branch December 13, 2025 09:04
@l0b0
Copy link
ContributorAuthor

l0b0 commented Dec 13, 2025

In the future, just add the backport label for a PR you want to backport

Thanks, but:

  • How do I do that? I don't have a side menu with labels on this MR.
  • The readme only says "If you need a module to be backported, then feel free to open an issue."
  • The "Backporting" section of the maintainer docs says to follow the process I did.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@l0b0@khaneliman