ansible-cmdb: init at 1.31, python3Packages.jsonxs: init at 0.6

[tie]

Description of changes

Packages http://github.com/fboender/ansible-cmdb

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:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• 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/)
• 24.11 Release Notes (or backporting 23.11 and 24.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.

---

Add a 👍 reaction to pull requests you find important.

[tie]

Result of nixpkgs-review pr 317405 run on aarch64-linux 1

6 packages built:

• ansible-cmdb
• ansible-cmdb.dist
• python311Packages.jsonxs
• python311Packages.jsonxs.dist
• python312Packages.jsonxs
• python312Packages.jsonxs.dist

[felbinger]

I got some comments earlier that the pr titel and commits should include python3Packages., so I suggest updating your pr title to: python3Packages.jsonxs: init at 0.6; python3Packages.ansible-cmdb: init at 1.31 and you'r second commit to python3Packages.ansible-cmdb: init at 1.31

[felbinger]

It can also be build on x86_64-linux

Result of nixpkgs-review pr 317405 run on x86_64-linux 1

6 packages built:

• ansible-cmdb
• ansible-cmdb.dist
• python311Packages.jsonxs
• python311Packages.jsonxs.dist
• python312Packages.jsonxs
• python312Packages.jsonxs.dist

[tie]

I got some comments earlier that the pr titel and commits should include python3Packages., so I suggest updating your pr title to: python3Packages.jsonxs: init at 0.6; python3Packages.ansible-cmdb: init at 1.31 and you'r second commit to python3Packages.ansible-cmdb: init at 1.31

The ansible-cmdb package is not in the python3Packages package set (it’s an application, not python package), so it shouldn’t be prefixed. W.r.t. PR title, it’s the first time I’m hearing about this convention and I don’t think it’d scale to a more complex change sets, but I guess it’s fine since there are only two small init commits.

[felbinger]

I got some comments earlier that the pr titel and commits should include python3Packages., so I suggest updating your pr title to: python3Packages.jsonxs: init at 0.6; python3Packages.ansible-cmdb: init at 1.31 and you'r second commit to python3Packages.ansible-cmdb: init at 1.31

The ansible-cmdb package is not in the python3Packages package set (it’s an application, not python package), so it shouldn’t be prefixed. W.r.t. PR title, it’s the first time I’m hearing about this convention and I don’t think it’d scale to a more complex change sets, but I guess it’s fine since there are only two small init commits.

I see, my bad I oversaw this. I agree but I got these comments earlier on one of my pr's.

[JohnRTitor]

Additionally please format your files with nixfmt-rfc-style

[tie]

Done.

[JohnRTitor]

Result of nixpkgs-review pr 317405 run on x86_64-linux 1

6 packages built:

• ansible-cmdb
• ansible-cmdb.dist
• python311Packages.jsonxs
• python311Packages.jsonxs.dist
• python312Packages.jsonxs
• python312Packages.jsonxs.dist

[JohnRTitor]

LGTM

[github-actions]

Successfully created backport PR for release-24.05:

• [Backport release-24.05] ansible-cmdb: init at 1.31, python3Packages.jsonxs: init at 0.6 #325081