is there a process for deprecating a package?

Not that I know of, sadly.

Well, yeah, seems like there is no way. It seems that adding "(deprecated)" to the description of the package would be the first step.

We should definitively not just remove the package, as this might break nixos updates for people. I'd rather set the description to "(deprecated)" and, in the next release (nixos-20.03) remove rtv, but not like in the middle of the nixos year.

Maybe I would even schedule the removal for 20.09 rather than 20.03, because rtv still works afaik.

I agree with @matthiasbeyer that we should keep rtv while it works.

Not that I know of, sadly.

IIRC we basically throw an error (as you did) and add a note in the release-notes for the upcoming release.

@filalex77 now that #75817 is merged can you please update this PR to mention tuir and then we can merge? @Ma27 - sound good to you?

Hello, I'm a bot and I thank you in the name of the community for your contributions.

Nixpkgs is a busy repository, and unfortunately sometimes PRs get left behind for too long. Nevertheless, we'd like to help committers reach the PRs that are still important. This PR has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.

If this is still important to you and you'd like to remove the stale label, we ask that you leave a comment. Your comment can be as simple as "still important to me". But there's a bit more you can do:

If you received an approval by an unpriviledged maintainer and you are just waiting for a merge, you can @ mention someone with merge permissions and ask them to help. You might be able to find someone relevant by using Git blame on the relevant files, or via GitHub's web interface. You can see if someone's a member of the nixpkgs-committers team, by hovering with the mouse over their username on the web interface, or by searching them directly on the list.

If your PR wasn't reviewed at all, it might help to find someone who's perhaps a user of the package or module you are changing, or alternatively, ask once more for a review by the maintainer of the package/module this is about. If you don't know any, you can use Git blame on the relevant files, or GitHub's web interface to find someone who touched the relevant files in the past.

If your PR has had reviews and nevertheless got stale, make sure you've responded to all of the reviewer's requests / questions. Usually when PR authors show responsibility and dedication, reviewers (privileged or not) show dedication as well. If you've pushed a change, it's possible the reviewer wasn't notified about your push via email, so you can always officially request them for a review, or just @ mention them and say you've addressed their comments.

Lastly, you can always ask for help at our Discourse Forum, or more specifically, at this thread or at #nixos' IRC channel.

I marked this as stale due to inactivity. → More info

Should still be removed (marked as deprecated).

#133085 already removed.