does not mirror bzr branches over ftp

Jono, is there a reason why we don't mirror from FTP?

I can't think of one. It looks like this was introduced by accident when we re-vamped the puller to improve stacking. We went from blacklisting URL schemes to whitelisting them and missed FTP.

Also...

<jelmer> "Launchpad has not been able to mirror this branch. The last attempt was 1 minute ago. (Launchpad does not mirror ftp:// URLs.) Launchpad will try again in 11 hours. If you have fixed the problem, please ask Launchpad to try again."
 Will do, thanks
 I like how it says it's going to retry in 11 hours.. perhaps it hopes it will have ftp:// support by then ? ;-)
<lifeless> well it accepted the url, so its not blascklisted
 its likely just a firewall hole that needs punched for the new machine
 spm: ^
<spm> lifeless: is a firewall issue
<lifeless> spm: if the old machine had it open, it should be a no-brainer to open for the new ? :>
<spm> errr - no. :-) Different network.
 fwiw, this came out in the migration. it was determined we had approx 2-5? ftp:// (attempted) mirrors - none of which ever worked. So the 'ftp' access was left... broken I suppose.

I'm not actively working on this.

Fixed in stable r14878 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/14878>.

This seems to somewhat work - we actually call the right code in bzr but the packets seem to be filtered.

I'm marking this as qa-ok since it doesn't shouldn't block deployment.

This is fixed in the code, but for some reason it's still failing. I suspect it's related to proxies.

Unassigning, since I'm not working on resolving this at the moment.

(I was trying to fix this as a drive-by, since I was changing the URL verification code anyway to support 'bzr://').