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]

Enlistment failed for /p/nvda - step 1 of 3 (Bzr)

Closed

Hi,
NVDA has recently moved from Sourceforge to self-hosted Bazaar (obviously keep the old SF enlistment, for the history).

I tried to add the new enlistment and it failed. Please can you take a look. I tried various URLs, and this seemed the most suitable (don't know much about Bazaar, so could well be wildly wrong!)

(BTW, I imagine you're having fun with the vast choice of new DVCSs, and the variety of people's hosting solutions!)

Keep up the great work. Cheers,

Nick

Nick Freear over 13 years ago

Nick,

I seem to be striking out on both counts with this project. First, I re-fetched the BZR enlistment successfully, but ran into trouble later on in the process. Will submit that one to loftier heads to ponder...

Then I noted that the Sourceforge SVN enlistment hadn't been updated for two months. Rescheduled that job and found out that this repo is now among the missing. Please check this out for me and let me know.

Problem is, if this SVN isn't going to come back, there's no point in keeping it. It will stop any forward motion with the BZR enlistment once we get it working properly. Unfortunately, with our system here, it's all-or-none!

Thanks and more later!

ssnow-blackduck over 13 years ago

Hi Nick,

I know it's been a very long time, but we've finally sussed out the problem here.

During the conversion to Subversion to Bazaar, some of the revisions were given unfortunate unique IDs that include the substring '..'. This sequence has special meaning to Bzr, and causes problems when we pass the the IDs to the Bzr command line tools.

This is now Bzr bug 827223.

I'm not sure yet of any good workaround on our end, so I'm hopeful that something can be done in Bzr itself.

Thanks,
Robin

Robin Luckey over 12 years ago

We deployed new bzr adapter couple months ago which has fixed this problem.

Abhay Mujumdar about 12 years ago

Comments to this topic are now closed. Please create a new topic to get technical support.

The user who created the topic can reopen this topic at any time.