How should we handle conflicting information between nixpkgs revisions?

[Erethon]

We've ran into a situation that I think the current user model can't handle.

There exists a maintainer that has changed GitHub accounts (and thus GitHub IDs), but has renamed their new GitHub account to have the username of the old one. This is an issue for us, because in certain channels this change isn't reflected yet and based on which channel we ingested last the NixMaintainer object will either point to the old GitHub user or the new one and we can support only one.

I'm not sure what the solution for this should be, any ideas what's the best way to model this?

[fricklerhandwerk]

@balsoft proposed we should take the information from nixpkgs-unstable. @Erethon argues that the conflict may just well be between revisions of the same branch.

Related:

• Determine maintainer status only at the tip of each channel #627 (comment)

[wolfgangwalther]

we should take the information from nixpkgs-unstable.

Very much agree with this. I came across this in NixOS/nixpkgs#481891, where I was pinged, but I am not a maintainer of the package anymore. Maintainer information is very often not backported to the stable branches, so the unstable branch really is the only relevant source of maintainer information.

[fricklerhandwerk]

Closed by #627