Fixing the Perlbal cvs warnings

[foxfirefey]

So, today I tried to sync code (I used a dws script) and got this error:

Mercurial directory 'perlbal' doesn't exist under /home/dw/cvs. Re-run vcv with --checkout for me to automatically get it for you.

I *think* I've fixed it by going into the cvs directory and:

rm -rf perlbal
vcv --checkout --conf=multicvs.conf

And then doing the regular sync. I'm posting about it in case anybody else is running into this issue. Relevant changelog entries: cloning Perlbal repository, so that this change could be made.

Comments

[mark]

You run vcv manually, as opposed to bin/cvsreport.pl?

[foxfirefey]

Not generally, no! Only while I was trying to figure out what to do to fix this. I could have gone about it the wrong way.

[kareila]

I had to use much the same workaround.

cvsreport.pl didn't allow me to access the --checkout option that vcv wanted, and just running the vcv command fails if you don't move the old directory out of the way first.

[sophie]

The error message says "vcv" specifically - "Re-run vcv with --checkout for me to automatically get it for you." - so it's not surprising to me, personally.

I wonder if there's a better way of doing something with that error message.

[sophie]

Hmm. cvsreport.pl worked fine with the --checkout option when I had to fix mine.

How did you do yours?

[exor674]

Well vcv is the generic tool, so modifying that might be stupid,

[afuna]

I had problems running the --checkout (of both cvsreport.pl and vcv) until I removed the old directory, hehee.

[sophie]

That's why I didn't say to just edit it to say cvsreport.pl.

I was thinking maybe if there was a way for vcv to tell it had been run from cvsreport.pl, it may work out.