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

wal-lang: init at rev 06498c3f5341ce687a37ad52647f300b72dff52a #266305

Closed
wants to merge 2 commits into from

Conversation

Avimitin
Copy link

@Avimitin Avimitin commented Nov 8, 2023

Description of changes

This PR adds three new packages wal-lang, lark-parser and pylibfst. lark-parser and pylibfst are required by wal-lang, but not presented in python-modules. And we need to use the HEAD revision because the latest release of the wal-lang repository is missing features and has some of the dependencies with security issues.

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/)
  • 23.11 Release Notes (or backporting 23.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.

@NixOSInfra NixOSInfra added the 12. first-time contribution This PR is the author's first one; please be gentle! label Nov 8, 2023
pkgs/development/python-modules/lark-parser/default.nix Outdated Show resolved Hide resolved
pkgs/development/python-modules/lark-parser/default.nix Outdated Show resolved Hide resolved
pkgs/development/python-modules/lark-parser/default.nix Outdated Show resolved Hide resolved
pkgs/development/python-modules/pylibfst/default.nix Outdated Show resolved Hide resolved
pkgs/development/python-modules/pylibfst/default.nix Outdated Show resolved Hide resolved
pkgs/development/python-modules/wal-lang/default.nix Outdated Show resolved Hide resolved
pkgs/development/python-modules/wal-lang/default.nix Outdated Show resolved Hide resolved
pkgs/development/python-modules/wal-lang/default.nix Outdated Show resolved Hide resolved
@Avimitin
Copy link
Author

Avimitin commented Nov 8, 2023

Changes are all applied. Please make a new review.

@MikaelFangel
Copy link
Contributor

The commit adding you as a maintainer should be the first commit of this PR with the format:
maintainers: add <handle>

@Avimitin
Copy link
Author

Avimitin commented Nov 8, 2023

Should be fixed. Thanks for your review.

@Avimitin Avimitin changed the base branch from nixos-unstable to master November 8, 2023 18:05
@Avimitin
Copy link
Author

Avimitin commented Nov 8, 2023

Seems like that I can only change the base branch. Is it ok to merge this PR? Or should I open a new one?

@MikaelFangel
Copy link
Contributor

MikaelFangel commented Nov 8, 2023

A member with the right privileges needs to approve the checks and only a member with merge privileges (not me) can merge this PR. Besides I think other more experienced members also should review this so it follows all the guidelines (:

And forgot to say thank you for your contribution to nixpkgs 🎉

@Avimitin
Copy link
Author

Avimitin commented Nov 8, 2023

Ok I get that. Anyway, thanks for your review :).

Copy link
Member

@leo60228 leo60228 left a comment

Choose a reason for hiding this comment

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

This should probably be split into multiple commits, and I think the commit message should be formatted like "wal-lang: init at unstable-2023-08-12".

Additionally, while I don't know much about the project being packaged and using an unstable version might be standard, would it be possible to use a stable release with the dependency updates backported? I assume there's a reason that the new features aren't in a release yet, and Nixpkgs generally packages stable versions when possible.

@@ -0,0 +1,18 @@
{ lib, fetchPypi, buildPythonPackage }:
buildPythonPackage rec {
Copy link
Member

Choose a reason for hiding this comment

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

There's an extra space at the beginning of this line.

@Avimitin
Copy link
Author

Avimitin commented Nov 8, 2023

would it be possible to use a stable release with the dependency updates backported?

Umm that means we have to maintain a patch for this. Using latest commit will be more convenient. But actually it is stable enough, maybe I should go to upstream and ask them to release a new version.

@Avimitin
Copy link
Author

Avimitin commented Nov 8, 2023

Seems like the No channel PR action cannot pass successfully. Maybe I should open a new branch and new PR for this package?

@Avimitin
Copy link
Author

Avimitin commented Nov 8, 2023

Closed the PR for now. I will try to argue with upstream to get new release. And thanks for your review and suggestions! :)

@Avimitin Avimitin closed this Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6.topic: python 12. first-time contribution This PR is the author's first one; please be gentle!
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants