edgedb: 3.4.0 -> 4.0.2

[ahirner]

• update default.nix src
• update Cargo.lock

Description of changes

I wonder if Cargo.lock can be de-vendored, since it built with ${src}/Cargo.lock in a flake of mine as well.
The discussions in #221716 go into some depths, but I couldn't find a quick answer.

nix shell .#edgedb
edgedb -V
edgedb project init
# ...
edgedb
select "foo";
# {'foo'}
\quit
edgedb instance destroy -I nixpkgs --force
rm -rf dbschema
rm edgedb.toml

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.05 Release Notes (or backporting 23.05 and 23.11 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.

[kirillrdy]

I've asked a question in #221716, using Cargo.lock from src seems to be working

[ahirner]

Unlike what ofborg suggests, ${src}/Cargo.lock comes into existence on my machine. I'm not a "nix-pert" enough to say whether it was realized from other builds or so.

$ nix-store --query --referrers-closure /nix/store/f1qwbypqxv2xvkqpqf25p4h49j6caaj3-source
/nix/store/f1qwbypqxv2xvkqpqf25p4h49j6caaj3-source
/nix/store/ajfzjh6wlq4dl2l58mzc6dbn7xk412va-cargo-vendor-dir

I guess I revert 00dcab4 and then it's good to go? @kirillrdy @ranfdev

[kirillrdy]

Unlike what ofborg suggests, ${src}/Cargo.lock comes into existence on my machine. I'm not a "nix-pert" enough to say whether it was realized from other builds or so.

$ nix-store --query --referrers-closure /nix/store/f1qwbypqxv2xvkqpqf25p4h49j6caaj3-source
/nix/store/f1qwbypqxv2xvkqpqf25p4h49j6caaj3-source
/nix/store/ajfzjh6wlq4dl2l58mzc6dbn7xk412va-cargo-vendor-dir

I guess I revert 00dcab4 and then it's good to go? @kirillrdy @ranfdev

yeah sorry I forgot to follow up,

"${src}/Cargo.lock" will trigger import from derivation which is disabled in hydra/ofborg to speed up eval time.

you can test this locally by adding

          allow-import-from-derivation = false

into your nix.conf

so yes, revert devendering of lock file

[ranfdev]

I'm sorry, I can't follow this. Could you remove me from the maintainers list? Thanks

[ahirner]

maintainers list

Are the thumbs up a vote for emtpy maintainer list or for @kirillrdy to step up? Not sure if an empty list is acceptable ;)

[kirillrdy]

maintainers list

Are the thumbs up a vote for emtpy maintainer list or for @kirillrdy to step up? Not sure if an empty list is acceptable ;)

empty list for existing package is acceptable. @ahirner if you are actively using edgedb then I would recommend you to add yourself as maintainer. I am happy to be added as well. ( if you add yourself or not )

[ahirner]

using edgedb ... happy to be added as well

Sounds great! I know the package but not enough of nix(pkgs).

[kirillrdy]

@ahirner can you either squash commits, eg all maintainer related commits squashed.

as for hash change can be own commit ( or squashed ) just need to update commit message so that it matches contribution guidelines

[kirillrdy]

apologies, i kinda told you a wrong thing

• maintainers: add ahirner
• edgedb: 3.4.0 -> 4.0.2
• edgedb: update maintainers