Launchpad itself

svn vcs-import for paparazzi broken

Asked by Felix Ruess

The subversion repo of savannah was down for a while but is back up now.
Since then the import of http://svn.savannah.gnu.org/svn/paparazzi/paparazzi3/trunk always fails with a checksum error.

svn: Checksum mismatch for 'conf/settings/csc_ap.xml'; expected: '6e780045eb32d3560c3723c67dd16f06', actual: 'b2894a495073c77b844b2063a2a86a32'

The svn repository works fine, whether using svn or bzr checkout http://svn.savannah.gnu.org/svn/paparazzi/paparazzi3/trunk

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
Michael Hudson-Doyle Edit question
Solved by:
Michael Hudson-Doyle
Solved:
Last query:
Last reply:
Whiteboard:
Assigned to Michael Hudson.
Revision history for this message
Jeroen T. Vermeulen (jtv) said : 		#1

To help out the person who will look at this, I take it it's this branch on Launchpad? https://code.launchpad.net/~vcs-imports/paparazzi/trunk

Revision history for this message
Felix Ruess (flixr) said : 		#2

Yes, that is the correct branch. Sorry... my bad. Should have included that information right away.

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

Well, that was a little strange -- svn up in the checkout the code import system was failing. Maybe the repository was manually edited?

In any case, I blew that away and replaced it with a fresh checkout and it seems to be at least getting somewhere now.

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

And now it still doesn't work :(

The only thing that springs to mind is to abandon the current import and try to import it again, which will be inconvenient if you have branches based on this import. Let me know if that's what you want to do.

Revision history for this message
Felix Ruess (flixr) said : 		#5

It might be the case that the savannah hackers edited the repository manually when they tried to restore everything after the crash.
As it is more inconvenient not to have a working import it would be great if you could just try to make a completely fresh import.
Thanks!

Revision history for this message
Celso Providelo (cprov) said : 		#6

Felix,

That you can do by yourself, Drop the VCS import and reset paparazzi trunk with a new one.

You may try this procedure in staging first:

https://code.staging.launchpad.net/~vcs-imports/paparazzi/trunk

If it all works as expected, perform it again on production and I will promptly approve the new import.

Revision history for this message
Felix Ruess (flixr) said : 		#7

How do I drop the VCS import?
I can only link a different branch to the trunk series.

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

I started a new import at https://code.edge.launchpad.net/~vcs-imports/paparazzi/trunk
The old one is now at https://code.edge.launchpad.net/~vcs-imports/paparazzi/trunk-old

Let's see how this goes.

Revision history for this message
Felix Ruess (flixr) said : 		#9

Thanks Michael!
Looking good. You can remove trunk-old.

Revision history for this message
Felix Ruess (flixr) said : 		#10

Thanks Michael Hudson, that solved my question.