Skip to content

Conversation

@FliegendeWurst
Copy link
Member

  • move to finalAttrs pattern
  • avoid using pname
  • use tag instead of rev
  • add meta.changelog
  • do not repeat package name in meta.description per style guidelines

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.

@FliegendeWurst FliegendeWurst requested a review from Izorkin April 21, 2025 20:21
@github-actions github-actions bot added 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux. labels Apr 21, 2025
@wegank wegank added the 12.approvals: 1 This PR was reviewed and approved by one person. label Apr 22, 2025
@Sigmanificient
Copy link
Member

Why not moving it to pkgs/by-name aside nghttp2?

@FliegendeWurst FliegendeWurst force-pushed the nghttp3-modernize branch 2 times, most recently from 9ff2e29 to b3bea81 Compare April 26, 2025 12:42
@FliegendeWurst
Copy link
Member Author

This will now create a trivial merge conflict on staging, but it should be okay.

@github-actions github-actions bot added 10.rebuild-darwin: 11-100 This PR causes between 11 and 100 packages to rebuild on Darwin. and removed 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. labels Apr 26, 2025
@Sigmanificient
Copy link
Member

This will now create a trivial merge conflict on staging, but it should be okay.

I didn't know sorry 😅

Copy link
Member

@Sigmanificient Sigmanificient left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Diff LGTM

@wegank wegank added 12.approvals: 2 This PR was reviewed and approved by two persons. and removed 12.approvals: 1 This PR was reviewed and approved by one person. labels Apr 29, 2025
@Aleksanaa Aleksanaa added the 2.status: merge conflict This PR has merge conflicts with the target branch label May 15, 2025
@wegank wegank added 12.approvals: 3+ This PR was reviewed and approved by three or more persons. and removed 12.approvals: 2 This PR was reviewed and approved by two persons. labels Jun 9, 2025
@wolfgangwalther
Copy link
Contributor

This has mostly trivial changes, three approvals - and a merge conflict.

@MattSturgeon
Copy link
Contributor

@FliegendeWurst I took the liberty of resolving the conflicts. Feel free to incorporate my patch into a rebase.

@nixpkgs-ci nixpkgs-ci bot added 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. and removed 2.status: merge conflict This PR has merge conflicts with the target branch 10.rebuild-darwin: 11-100 This PR causes between 11 and 100 packages to rebuild on Darwin. labels Aug 15, 2025
@wolfgangwalther
Copy link
Contributor

Rebased, which should also fix treefmt.

@wolfgangwalther wolfgangwalther merged commit e970daa into NixOS:master Aug 16, 2025
25 of 28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux. 12.approvals: 3+ This PR was reviewed and approved by three or more persons.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants