Comment 1 for bug 411642

This is fixed in later versions by using a standard method to optionally
get a working tree, rather than implementing it ourselves and failing to
handle all the cases.

In this case there is a working tree at that URL, but it is remote, so you
get a different exception than if there is no tree.

I've removed the tree from that location so you should at least be
able to build that package :-)

Thanks,

James