python3Packages.filecheck: 0.0.24 -> 1.0.1

[AntonLydike]

Update the version of the filecheck python package. This package has seen a change in maintainers and project location, as documented here in the old project.

I don't have a ton of experience with packaging for nix, so this is a first attempt and will probably need some revisions. Happy to implement needed changes.

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/)
• 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.

---

Add a 👍 reaction to pull requests you find important.

[AntonLydike]

Pinging @yorickvP as listed package maintainer

[AntonLydike]

(how are all the checks passing if the hash is all zeros?)

[jopejoe1]

Could you rename the commit message to python3Packages.filecheck: 0.0.24 -> 1.0.1 to follow commit conventions.

[jopejoe1]

This needs tobe changed into a real hash

[AntonLydike]

How do I go about obtaining such a hash? I seem to remember that "just put an empty string and look for the error message" was the common advice a while back, but this appears to not work anymore?

[jopejoe1]

In my local branch of nixpkgs I would generally try to build the package of which I want to get the hash of, and then it would throw an error message with the correct hash.

I generally use nix build for that, e.g. for this package it would be nix build .#python3Packages.filecheck which returns an error message with the correct hash in this case sha256-orOfrXqIT/qgwPtEcuuJSK3fwmdRPjx4LmzTshxNN0I=.

[AntonLydike]

@jopejoe1 Can you point me at how I can get the right hash for the build script? I was under the assumption that the build would fail with a wrong hash (and then print the expected value), but CI appears to succeed, even with a blank hash. What is the expected way of obtaining such a hash?

[mdaniels5757]

Can you point me at how I can get the right hash for the build script? I was under the assumption that the build would fail with a wrong hash (and then print the expected value), but CI appears to succeed, even with a blank hash. What is the expected way of obtaining such a hash?

@AntonLydike It looks like the correct hash is sha256-orOfrXqIT/qgwPtEcuuJSK3fwmdRPjx4LmzTshxNN0I= per https://github.com/NixOS/nixpkgs/pull/391568/checks?check_run_id=39728976447. The other way to get this is with nix-prefetch-git, which returns the same hash when run like so: nix-prefetch-git https://github.com/antonlydike/filecheck.git v1.0.1.

[sarahec]

@jopejoe1 Can you point me at how I can get the right hash for the build script? I was under the assumption that the build would fail with a wrong hash (and then print the expected value), but CI appears to succeed, even with a blank hash. What is the expected way of obtaining such a hash?

1. Check out the PR's branch
2. Since this is quite old, rebase atop master before building.
3. nix-build -A python313Packages.filecheck
4. The build will fail and print out the source package's hash. Copy and paste this into your derivation.