Update upstream git repository for safe-rm

[fmarier]

Gitorious is long gone and the upstream repository is now on Launchpad: https://code.launchpad.net/safe-rm

Motivation for this change

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Ensured that relevant documentation is up to date
• Fits CONTRIBUTING.md.

[SuperSandro2000]

There are other links which point to Gitorious. We should replace them, too if they are still available.

[SuperSandro2000]

Can you change the commit headline to?

safe-rm: Update git repository 

[fmarier]

Can you change the commit headline to?

safe-rm: Update git repository 

Updated.

[SuperSandro2000]

@SuperSandro2000 please avoid changing the base branch to avoid spamming tens of maintainers. Thank you :)

Sometimes it works but 3 out of 4 times it does not. I wish GitHub had a feature where I can just pick that one commit into another branch.

[roberth]

I wish GitHub had a feature where I can just pick that one commit into another branch.

That would be nice, but for now let's do that on the command line.

Did anyone try convert to draft before rebasing? Might be worth a shot.

[FRidh]

Sometimes it works but 3 out of 4 times it does not.

Yes, sometimes it works because we merge master into the other branches. We need a GH Action to do these merges more often #104594

[roberth]

@FRidh that doesn't work for cases where contributors target a release branch first instead of master, like this one.

[erictapen]

Backported to 20.09 in 471e36f.

[alyssais]

> @SuperSandro2000 please avoid changing the base branch to avoid > spamming tens of maintainers. Thank you :) Sometimes it works but 3 out of 4 times it does not. I wish GitHub had a feature where I can just pick that one commit into another branch.

I think if you reset to the merge base of the old and new branches, pick your commit onto that, force push, and then change the base branch, it won't spam anybody.