Can't remove link between project and source package

[Andrea Bedini]

Consider this situation :
Wrongly I link a release series of a project that doesn't exist in ubuntu to an ubuntu source package. What can I do ?

It seems I can't remove that link. Simply removing source package name in /+ubuntupkg form doesn't work.

[Steve Alexander (stevea)]

As an immediate remedy, we should fix the data in the production database.

[Christian Reis (kiko)]

bug #38829 is an example of this problem.

[Christian Reis (kiko)]

Pushing off because of SSO work.

[Guilherme Salgado (salgado)]

The +ubuntupkg page has a table at the bottom which lists all links from that product series to packages in any distro releases. I suggest adding another column with a button to delete the entries which takes the user to a separate page asking for confirmation. If we want to allow users to change the entries it may be better to have a link on each table row taking the user to a page where (s)he can change/delete the entry.

[David Allouche (ddaa)]

Not making it to 1.1.10, postponing to 1.1.11.

[Stéphane Loeuillet (leroutier)]

Isn't this bug also related to bug #156118 ?
('swfdec' source package in Ubuntu Gutsy while it has never been)

[David Allouche (ddaa)]

It is related, in that there is currently no user interface to remove the link between https://edge.launchpad.net/swfdec/+distributions and https://edge.launchpad.net/ubuntu/gutsy/+source/swfdec.

[David Allouche (ddaa)]

RF 5380

[Francis J. Lacoste (flacoste)]

Released in 1.1.12.

[Dennis Schridde (devurandom)]

Where am I supposed to find the "remove link" button?

https://launchpad.net/warzone2100/ - is linked to Breezy
https://launchpad.net/ubuntu/+source/warzone2100/ - shows delete buttons, but not for Breezy
https://launchpad.net/ubuntu/breezy/+source/warzone2100/+packaging - shows Breezy, but no delete button

[Matthew Paul Thomas (mpt)]

Dennis, you can find the "Delete Link" button at <https://launchpad.net/ubuntu/+source/warzone2100>. The problems you've discovered I've reported as bug 204119 and bug 204121.