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]
One bzr import failed, one svn import worked, all other svn imports not retried
Hi,
can you please have a look at https://www.ohloh.net/p/evolvis/enlistments and try to fix these imports?
Thanks!
Thorsten,
Have cleared most of the issues but we remain with three stubborn enlistments:
First, we have two related subversion enlistments that appear to now be password-protected. Checking on the web interface, I get a login page trying to look at the repositories as an anonymous user.
Second, there appears to be a bazaar repository which has some kind of corruption
which prevents our analysis.
I will send an e-mail with the details and in the case of the bazaar enlistment, perhaps you can pass it on to the forge management and ask for them to perform a sanity check to see if what we are observing is consistent with a corruption. In the case of the subversions, you may be able to assess the state of the two repositories and either enlist them with a read-only login/password (knowing that these may become public at any time) or have them returned to open status or remove the enlistments entirely.
I'll be sending the e-mail shortly.
Thanks!
Thanks for the quick answer!
I'll look at the svn ones (I can fix that, they should be viewable).
The bzr repo is not corrupt, but it can be converted/pushed to neither svn nor git because it triggers bugs in both bzr-svn and bzr-git (the former of which I have reported to them, the latter of which already was reported). That's the reason I added it in the first place, since I can no longer push it into svn… (I'll delete the respective svn branch from enlistments once the bzr one works.)
Thorsten,
Just doing a follow-up on this. I notice the following oddities (in the subversion that ends in evolvis):
We get to r1871 and the whole fetch unravels.
Bringing down r1870 yields a successful fetch of 1.17 Gb !!!
Current structure of repository wasn't in-place until r18761.
At r18760 the structure was:
branches/
plugins/
trunk/
README
and shouldn't be enlisted except for trunk. The previous incarnations that contained vendors/ were too sizable to swallow as well. The change-over from the structure seen above to the current structure will present some difficulty for us to follow. The whole subversion should be given a sanity-check especially at r1871 and beyond. Looks as if there's some corruption in there that is continued in later revisions.
Let me know...
Thanks!