Draupnir: init at 1.85.1

[TheArcaneBrony]

Description of changes

Draupnir is a hardfork of mjolnir. Mjolnir package has been unmaintained due to upstream bugs. This package is mostly a drop-in replacement. This package also uses newer methods of handling dependencies.

Repository can be found at:
https://github.com/the-draupnir-project/Draupnir

Note on testing: package/module was tested in our production environment, works fine as far as it's been used.
Note on replacing mjolnir: Not sure whether this is appropriate, due to general usage of the bot changing. You can however fully automatically migrate from mjolnir to draupnir.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• 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/)
• 23.05 Release Notes (or backporting 22.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.

[apfelkuchen6]

This successfully builds for me on x86_64-linux and aarch64-linux. I did not try the module.

This should be rebased such that this PR has the following commits (in this order):

1. maintainers: add Rory
2. lib/licenses: add CSL
3. draupnir: init at 1.81.1 (which adds the package with its update script and adds it to the package lists)
4. nixos/draupnir: init (which adds the module with the documentation and adds it to the module list)

[apfelkuchen6]

ideally, this would be sorted (in its category), but this is a lost cause by now.

[TheArcaneBrony]

Any suggestions where I'd put it then?

[alyssais]

@TheArcaneBrony do you plan to address the review comments, e.g. the one about the license?

[TheArcaneBrony]

Yes, I just haven't gotten around to it.

[mweinelt]

@ofborg eval

[TheArcaneBrony]

@ofborg eval

[TheArcaneBrony]

Meanwhile, can confirm this builds and runs on my system:

[mweinelt]

Yeah, I'm aware it builds, the problem is IFD, which is not allowed in nixpkgs.

[TheArcaneBrony]

Correct, which has been fixed as of this last commit.

[mweinelt]

Please rebase and squash the changes from

draupnir: Add recommended change

into the relevant commits.

[mweinelt]

It still conflicts with master. Can you fetch the remote and rebase again?

[gaykitty]

Ops I think I messed up something when I tried to push the rebased commits

[wegank]

I didn't do the merge either...

[gaykitty]

Yeah I'm not sure what happened. I was just trying to help @TheArcaneBrony with the rebase.

[mweinelt]

GitHub doing GitHub things 😫

Please open a new PR.

[mweinelt]

I salvaged and cleaned up the branch over in https://github.com/mweinelt/nixpkgs/tree/draupnir if you want to continue working on that.

[mweinelt]

Note that my interest is due to being a member of both the infrastructure and moderation team, and the lack of maintenance on Mjölnir, which we are currently using. It would be awesome to get Draupnir into nixpkgs and set up for our purposes!

[TheArcaneBrony]

While I'm aware all i needed to do for the most part was rebase on master and re-open the PR, I haven't gotten around to doing so due to some mental health complications. Did you make any changes on your branch? I checked and didn't notice any.

[mweinelt]

No, I just squashed the commits that were on top into the relevant commits.

[TheArcaneBrony]

Ah, that's what @gaykitty had done as well.
I think the flake/module is ready to be merged? I can't think of anything that needs to be changed.
Feel free to make the PR and merge if you think it's ready.

[TheArcaneBrony]

Though, would be interesting if there was a way to specify multiple Matrix accounts and/or preferred contact method in the maintainers list.