What can I do when Launchpad shows a wrong upstream connection?

Solution 1:

I don't think Launchpad will allow me to change the upstream connection myself.

It does - that's what the yellow icon next to the upstream link is (the red icon is for removing the link). The link is obviously wrong, so I have gone ahead and removed it, so now Launchpad shows this instead:

I don't think there's a project registered on Launchpad for the file command. Now:

• Anybody can register a project, but of course it's preferable if someone actually involved with the project creates it.

• There's no actual need for an upstream project for file to be registered in Launchpad: I doubt they will use it for announcements, code releases, bug tracking or anything else that LP offers.

• If you feel that an upstream project should exist, I'd ask the maintainer of the package about the best course of action (maybe they can create the project, or ask someone from upstream if they're interested). But:

  Christoph Biedl does not use Launchpad. This page was created on 2011-09-07 when the certificatepatrol package was imported into Sid.

This is not a bug with LP - projects and upstream connections are created by LP users, so this is likely user error.

I suggest that you ask the maintainer by posting a question on LP (questions can be converted to bugs and vice versa, if needed), but clearly nobody involved with file is interested in LP, so why bother?

You could also ask the LP Registry Administrators team to make a dummy project for file:

We own and register many projects in Launchpad, but we are always looking to hand them off to their official owners.

They own projects like coreutils (whose maintainers also probably have no interest in a presence on LP).