Launchpad claims Debian developers maintain Ubuntu packages and have uploaded packages to PPAs (when they have not)

The page mentioned display sources and you are checking the binary.

{{{
$ apt-cache showsrc pdmenu | grep Maintainer
Maintainer: Joey Hess <email address hidden>

$ apt-cache show pdmenu | grep Maintainer
Maintainer: Ubuntu MOTU Developers <email address hidden>
Original-Maintainer: Joey Hess <email address hidden>
}}}

That said, I agree that there is room for improvements in this source/binary duality. Let me think a bit about it.

OTOH, https://launchpad.net/~kitterman/+related-software lists packages that I maintain in Debian and also Ubuntu. I'd find it unfortunate if that went away (Personally, I'd like an uploaders section too).

Setting aside the source/binary question (which may make some parts of this bugs in pkgbinarymangler), might it make sense to use some filter criteria to meet both use cases? Perhaps limiting the concept of Maintainer to those who are in ~ubuntu-dev, or ~ubuntumembers, or have previously been listed as Changed-By: in an upload to Soyuz, and using defaults for others? Note that this may remain broken for teams, but that is a less common case.

Speaking as someone else who participates in Debian/Ubuntu collaborative teams, and is sometimes listed as an Uploader, it would be interesting to also capture this header if display of Maintainer is preserved based on synchronised source packages.

See also bug 30954, "Provide information for Debian maintainers about their packages in Ubuntu".

Of the bugs here, we have fixed part of it - we don't show the maintainer on the referenced package page now and on joeyh's page we correctly show uploads to debian. However PPAs are showing bogus data, so fixed and narrowed the description to that.

https://launchpad.net/ubuntu/+source/pdmenu still says Joey Hess is the pdmenu
maintainer in Ubuntu, so I don't think this is as fixed as you claim.

Content got shuffled around, I've reinstated that aspect of the bug - thanks.

Of course, the bogus PPA data may be due to users uploading tings with maintainer set wonkily, which LP cannot do anything about :(.

As recently as yesterday I got comments in the Debian BTS about bugs in an old PPA upload that had already been fixed in Debian Unstable (and Ubuntu Oneiric). I think it would be useful to mangle the maintainer address to the the email of the PPA owner for PPA uploads. That's who people should be contacting.

Oneiric/Precise in my last comment (not that it matters much for the purposes of this bug)

Mangling is certainly an option. We'll need to not break the security
PPPA though.

I suspect doing it only for public PPAs would be sufficient. For the private
ones I think it's unlikely to be an issue.

What about the public security PPAs? The toolchain PPAs? etc.

Do toolchain PPA packages get copied into official archives?

There would have to be some exceptions.

Perhaps we can move the things which will copy into Ubuntu itself to
be derived distros rather than PPAs. This is AIUI the long term
evolution planned for PPAs anyhow...

> This is AIUI the long term evolution planned for PPAs anyhow...

Whut? It is? News to me.

See also bug #403510 which is almost certainly a duplicate.