Forums : Technical Issue Help

Dear Open Hub Users,

We’re excited to announce that we will be moving the Open Hub Forum to https://community.blackduck.com/s/black-duck-open-hub. Beginning immediately, users can head over, register, get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.


On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at [email protected]

SourceForge CVS: The cvs server did not respond to an 'ls' command.

Hello.

I'm the manager of the EmuTOS project (id: emutos).
I noticed that the CVS activity had not been updated for a few years.
So I deleted the Code Location, then I'm not able to add it again.

On that page:
https://www.openhub.net/p/emutos/enlistments

I enter the source control URL:
:pserver:anonymous:@emutos.cvs.sourceforge.net:/cvsroot/emutos

As well as the CVS module name:
emutos

Then it fails with the error message:
The cvs server did not respond to an 'ls' command. Are the URL and module name correct?

I found that error in various forum posts, but no solution.

What can I do ?

Vincent Rivière about 11 years ago
 

Vincent,

Go to the edits page of the project and undo your deletion of the enlistment. That doesn't require any pre-qualification of the repository but should (!) pick up right from where it left off. Your mileage may vary. Let me know here if it doesn't work.

Thanks!

P.S. I wish I thought of that this morning but I don't think as clearly without loads of caffeine!

ssnow-blackduck about 11 years ago
 

Thanks for your suggestion.

I went there:
https://www.openhub.net/p/emutos/edits

But unfortunately, my removal of the Code Location is not present on that list. So I can't undo it.

Note that I removed the initial Code Location because the CVS activity had not been fetched by Open HUB during the last year. I hoped that a Code Location reset would help, but now the situation seems to be worse...

Vincent Rivière about 11 years ago
 

Vincent,

Have updated you via e-mail but will also report in here:

Good news. The update process has started on the CVS enlistment.
Should it finish, it will add 777 commits. Will report back with any progress.

Standby and thanks!

ssnow-blackduck about 11 years ago
 

Vincent,

Update finished OK (777 added commits). Analysis is now at August 05, 2014 on code collected on August 05, 2014 and last commit is at August 04, 2014 - about 12 hours ago.

Please remind me here if the project goes astray again.

Thanks!

ssnow-blackduck about 11 years ago
 

Many thanks, it works perfectly now :D

Vincent Rivière about 11 years ago
 

Vincent,

It's no problem. There's reportedly a bug in the initial ls command we send when we're pre-qualifying a new CVS (or subversion) enlistment. We're hoping that the mass-upgrades that we are planning with updated versions of all our tools will banish these bugs. It will take a while to test before we can roll out the upgrades to the live systems but hope to see it soon.

Thanks!

ssnow-blackduck about 11 years ago
 

I've actually the same issue with :pserver:[email protected]:/cvsroot/elem and elem, looks like this is not fixed so far?

Robert Scheck over 9 years ago
 

This is not fixed; I am running into the same problem.

From the technical point of view, the problem is, that the call to ls returns nil:
https://docs.omniref.com/ruby/gems/ohloh_scm/2.0.0/symbols/OhlohScm::Adapters::CvsAdapter/ls?d=139512801&n=0#line=22

Michael Aram over 9 years ago