vcs-imports fail in the presence of svn:externals
Bug #81684 reported by
David Allouche
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
David Allouche | ||
Bug Description
Imports from a subversion branch that uses the svn:externals property currently fail at the validation step.
We want to avoid importing the same data multiple times, so svn:externals are ignoring during the conversion process. However they are not ignored when doing the svn checkout that used for the validation cross-check.
So when svn:externals are used, the validation cross check will find differences and the import will fail.
This can be easily fixed, but the fix can lead to suprising results unless we also fix bug 68175.
Revision history for this message
| David Allouche (ddaa) wrote | #1 |
| Changed in launchpad-bazaar: | |
| importance: | Undecided → High |
| status: | Unconfirmed → Confirmed |
| Changed in launchpad-bazaar: | |
| assignee: | nobody → ddaa |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
Prevents a lot of imports from completing, for a known reason. High importance.