svn import fails when branch is created by a move

Bug #58029 reported by David Allouche
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
David Allouche

Bug Description

It looks like when a branch is created by a move (copy+delete) the initial imported revision is empty, which causes a failure on the first revision that tries to modify a pre-existing file.

In the case of the katapult import (svn://, the branch is created at revision 521764 by moving from /trunk/playground/utils/katapult:521763. The initial revision of the bzr import is an empty tree.

Tags: lp-code
David Allouche (ddaa)
description: updated
Changed in launchpad-bazaar:
importance: Untriaged → Medium
status: Unconfirmed → Confirmed
David Allouche (ddaa)
Changed in launchpad-bazaar:
assignee: nobody → ddaa
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers