Waiting for Import

[Charlie Poole]

Several of you have replied, so I'll answer all at once and explain
what I'm trying to do.

NUnit 3.0 is going to be a break from NUnit 2.x, with a new repository
started from scratch. I plan to put it on Launchpad.

It seemed like it might be useful in a few ways to make 2.5, which is
likely to be the last release in the 2.x series, available on LP as
a way of getting started on the platform. But if it proves too 
difficult, it's probably not the end of the world.

A one-shot conversion isn't what we planned, but it could be done that
way if we had to. I can get a tarball of the repository if you want to
try working from that.

Bottom line, this would help us but not being able to do it isn't 
a show-stopper - we would just have to wait for 3.0 to use LP.

Charlie

> -----Original Message-----
> From: Michael Hudson [mailto:michael.hudson at canonical.com] 
> Sent: Monday, April 21, 2008 1:34 PM
> To: Charlie Poole
> Cc: 'Christian Robottom Reis'; launchpad-users at lists.canonical.com
> Subject: Re: Waiting for Import
> 
> Charlie Poole wrote:
> > Thanks... It's not there yet. I can take an educated guess that the 
> > automated process may have run back against one of the 
> points where we 
> > manually edited the repository.
> 
> Actually, it's failing like this:
> 
> CRITICAL: received error response.
> CRITICAL: requested checkout of reporoot '/cvsroot/nunit', 
> file 'nunit20/src/tests/mock-assembly/AssemblyInfo.cs', 
> revision '1.12'
> CRITICAL: log of checkout responses follow.
> CRITICAL: "E cvs checkout: cannot create read lock in 
> repository `/cvsroot/nunit/nunit20/src/tests/mock-assembly': 
> No such file or directory\n"
> CRITICAL: "E cvs checkout: failed to remove lock dir 
> `/cvsroot/nunit/nunit20/src/tests/mock-assembly/#cvs.lock': 
> No such file or directory\n"
> CRITICAL: 'E cvs [checkout aborted]: read lock failed - giving up\n'
> CRITICAL: 'error  \n'
> 
> which isn't a failure mode that I've seen before.  It happens 
> in a different place each time we try it, which suggests that 
> there's some faint unreliability in the repository.  CSCVS 
> isn't very good at coping with this sort of thing :/
> 
> > I see no need to try to make sense
> > out of the history before those points - someone who cares 
> can always 
> > go back to CVS.
> 
> Unfortunately, with a mostly-automated conversion like this, 
> it's not really possible to say "import from this point on".  
> If you're after a one-shot conversion and/or have access to 
> the ,v files from the repository, there are other things we can try.
> 
> Cheers,
> mwh
>