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.synopsys.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]

gitorious git enlistment failing

Our main VM repository under

git://gitorious.org/cogvm/blessed.git fails to load.

Step 1 of 3: Downloading source code history (Failed 8 days ago.)

The very same repository is used in production over and over again.
One possible problem is that gitorious might throttle / blacklist the downloading agent if it pulls to quickly.The full repository history is more than 1 GB.

Camillo Bruni over 11 years ago
 

Camillo,

Having some trouble with the following command:

git clone -q -n 'git://gitorious.org/cogvm/blessed.git'

On my workstation, I get:

fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed

I can take a clone of the repo, though (452 mb).

Any ideas you might have? We need to do this for the operation of our analysis method.

Thanks!

ssnow-blackduck over 11 years ago
 

Hi,

We did not do any magic with the repository, so I can't explain that behvior
I will try with the stupid http protocol first and see if that helps.

thanks for having a look at this.

Camillo Bruni over 11 years ago
 

Ok no luck with https://git.gitorious.org/cogvm/blessed.git either.
It seems to work though if I limit the history --depth=100.

Camillo Bruni over 11 years ago
 

Camillo,

Unfortunately, we don't have that choice. It's all-or-nothing on our side. Perhaps you can contact gitorious support and ask them if there's a problem?

Thanks!

ssnow-blackduck over 11 years ago
 

Camillo,

I checked today and I guess that you've worked out the issue as seen above, but now I notice that another enlistment is failing. It appears there is no longer a master branch there... only a 2.0 and a 3.0 branch. Please choose one or enlist both or neither. This should clear the problem and resume processing (hopefully).

Thanks!

ssnow-blackduck almost 11 years ago
 

thanks for the feedback, I changed the repository descriptions, now they should be up to date...

Camillo Bruni almost 11 years ago