Re: QA Experiment: removing "stale uploaders"

[Louis-Philippe Véronneau <pollo@debian.org>]

On 2024-08-16 9 h 09 a.m., weepingclown wrote:
> Hi,
>
> This is a very reasonable thing to do considering the policy change. I also have two packages where I mistakenly ended up as the maintaner and DPT as uploader (see python-graphene-directives and python-graphene-federation) because of tooling defaults and me missing to see it in the end. I have been contemplating since I realized this about how urgently I should take care of this. What I mean is that, does this call for an immediate revision of the debian package, or is it sufficient to have a git commit to reverse it and then later upload it with the next possible upstream release. Thoughts?

Feel free to commit and not make a new release. I don't think anything 
is urgent.

> PS: And depending on how strictly we want to enforce this, there can perhaps also be a lintian warning/error?

Lintian can't be used to generate this kind of information, as it only 
has access to the source and binary packages, not the git history.

I feel relying on d/changelog for this doesn't provide enough information.

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   pollo@debian.org / veronneau.org
  ⠈⠳⣄