vcs import should report cvs config and svn externals information

Bug #68175 reported by David Allouche
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
Medium
Unassigned

Bug Description

Currently, cvs import ignores module configs and, in the future, svn imports will ignore externals (instead of failing when externals are used, bug 81684).

That means that imports from repositories that use these feature will be surprising because checking out the bzr branch will yield less data than checking out the cvs or svn branch it was imported from. Generally, such "incomplete" imports are not be able to build.

Transparent support for cvs configs or svn externals is possible, but it is not expected to be implemented in the foreseeable future.

When an import ignored a cvs config or svn external, the web page should report something like "The following externals definitions have been ignored: ..." so the user has the information to explain why the import appears incomplete, and to be able to build the complete nested tree.

Tags: lp-code ui
David Allouche (ddaa)
Changed in launchpad-bazaar:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
David Allouche (ddaa)
description: updated
Revision history for this message
David Allouche (ddaa) wrote :

Assigning to me as it is a code import problem.

Changed in launchpad-bazaar:
assignee: nobody → ddaa
Curtis Hovey (sinzui)
Changed in launchpad-code:
assignee: David Allouche (ddaa) → nobody
Tim Penhey (thumper)
Changed in launchpad-code:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers