Comment 10 for bug 878085

We renamed the project, so here are the logs from our failed imports:
https://code.launchpad.net/~mardy/opensesame-libaccounts-glib/trunk

We got around this problem by manually importing the git repository into bzr in my local machine, and then pushing that to LP; but in this way there is no indication in LP that the repository is an import of a remote one.
Such indication would be very helpful to direct contributors to propose their merge requests upstream, and not on the LP repository (though we can indeed handle them as well manually, having the contributors work upstream could save us some time).