code imports from launchpad itself should be refused at create time

[Jelmer Vernooij]

we don't allow code imports from launchpad itself for obvious reasons. However, the check for this is only present when the actual import happens, rather than when the import is created.

Ideally, Launchpad should immediately tell the user when they request an import from *.launchpad.net, and link to the bzr documentation on sprouting branches (which is presumably what the user is after)

[Robert Collins (lifeless)]

(the obvious reasons are both excessive use of resources and bypassing the access control checks for branches)

[Jelmer Vernooij (jelmer)]

So, we do actually refuse to import from launchpad.net already so there is no chance of bypassing the access control checks - we just don't tell the user until they have actually created the import and the import slave has processed it.

[Robert Collins (lifeless)]

there are a number of similar urls which could in principle reach our branches; we should add them to the blacklist ;)

[Jelmer Vernooij (jelmer)]

Sure, I'm all for that; I think that's a different issue though.