Launchpad itself

Fix ~vcs-imports/vpnc/trunk

Asked by Martin von Gagern

Hi! Would someone from the vcs-imports team please be so kind as to have a look at the vpnc import https://code.launchpad.net/~vcs-imports/vpnc/trunk and try to get it working again, either by simply reactivating the import or by deleting/renaming and re-importing the branch? The upstream SVN seems to work well enough, and has almost a hundred commits more than the last successful import from half a year ago. Thanks!

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
Michael Hudson-Doyle Edit question
Solved by:
Paul Hummer
Solved:
Last query:
Last reply:
Whiteboard:
Danilo on 2008-12-16: Michael, can you take a look at this and comment appropriately?
Revision history for this message
Best Paul Hummer (rockstar) said : 		#1

I believe this error is related to bug 120977. I don't think this error would be fixed by deleting the import and re-importing. However, the import system has been gradually getting an overhaul in which most of these types of bugs will be getting fixed in the next month of so.

Revision history for this message
Martin von Gagern (gagern) said : 		#2

bug 120977 talks about issues that seem specific to CVS to me. The vpnc import however is from SVN, and SVN has neither a strong concept of a MAIN branch nor of dead files. Thus the bug does not apply.

I know that the vpnc people have been doing some modifications to their SVN service. I'm not sure how deep that went, but it might have been a complete log dump & replay, or a restored backup which lost a few commits, or something similar which might seem like a divergent modification to the import system, as the log seems to indicate.

Revision history for this message
Martin von Gagern (gagern) said : 		#3

Thanks Paul Hummer, that solved my question.

Revision history for this message
Michael Hudson-Doyle (mwhudson) said : 		#4

I think Paul probably meant https://bugs.edge.launchpad.net/launchpad-cscvs/+bug/121569.

I deleted the import and set it up again (at the same URL). Let's see if that works better.