bittorrent NixOS Test: Un-Uncomment seeder takedown

[tfc]

Description of changes

Back in 2019, I commented this line while porting the test from perl to python.
Just today i found out that it works (again?), so let's comment it in again.

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

[tfc]

@ofborg test bittorrent

[h7x4]

I haven't tested the changes, but I think the commit message looks a bit weird. According to the git log, it seems more conventional to use either nixos/tests: made xyz changes to <service> or nixos/tests/<service>: made xyz changes

[tfc]

I haven't tested the changes, but I think the commit message looks a bit weird. According to the git log, it seems more conventional to use either nixos/tests: made xyz changes to <service> or nixos/tests/<service>: made xyz changes

I adapted it to the convention from your description that you feel is less weird.

[tfc]

@ofborg test bittorrent