Open Hub
Black Duck Open Hub

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]

OSGeo Foundation projects are not updated

Hello, for most of the OSGeo Foundation projects, the analyze are not in-sync with the respective code locations.

List of individual project causing problem:

  • QGIS

  • MapServer

  • GDAL

  • GeoServer

  • GRASS GIS

  • GeoTools

  • GEOS

  • Mapbender

  • OSSIM

  • MapGuide Open Source

  • Feature Data Objects (FDO)

  • Community MapBuilder

  • Geomajas

  • rasdaman

  • OSGeo-Live

  • gvSIG Desktop 2

  • Opticks

  • pycsw

Can you please have a look at the problem?

Thanks,

Djay

djay about 9 years ago
 

Gerald,

No problem. I'll take a look sometime today (if the moons of Saturn are aligned with the ecliptic) otherwise first thing tomorrow. (You'd be surprised how many things there are that are not under the control of an administrator... :-)

Thanks!

ssnow-blackduck about 9 years ago
 

Gerald,

Interim report.

Re qgis: Analyzed on Friday, February 27, 2015 based on code collected on Thursday, February 26, 2015.

Re geos: Analyzed on Friday, February 27, 2015 based on code collected on Thursday, February 26, 2015.

Re: pycsw: Analyzed on Friday, February 27, 2015 based on code collected on Thursday, February 26, 2015.

More later as they finish.

Thanks!

ssnow-blackduck about 9 years ago
 

Thanks a lot for your help.

Unfortunately, there is still two projects not updating : GeoMOOSE and Opticks.

djay about 9 years ago
 

Gerald,

Re mapbender: Analyzed on Sunday, March 01, 2015 based on code collected on Sunday, March 01, 2015.

Re mapserver: Analyzed on Sunday, March 01, 2015 based on code collected on Sunday, March 01, 2015.

Re fdo: Analyzed on Sunday, March 01, 2015 based on code collected on Sunday, March 01, 2015.

Re communitymapbuilder: Analyzed on Sunday, March 01, 2015 based on code collected on Sunday, March 01, 2015.

Re geomajas: Analyzed on Sunday, March 01, 2015 based on code collected on Sunday, March 01, 2015.

Re gdal: Analyzed on Monday, March 02, 2015 based on code collected on Saturday, February 28, 2015.

Re geoserver: Analyzed on Monday, March 02, 2015 based on code collected on Sunday, March 01, 2015.

Re grass_gis: Analyzed on Monday, March 02, 2015 based on code collected on Saturday, February 28, 2015.

Re geotools: Analyzed on Monday, March 02, 2015 based on code collected on Sunday, March 01, 2015.

Re ossim: Analyzed on Monday, March 02, 2015 based on code collected on Sunday, March 01, 2015.

Re mapguide: Analyzed on Monday, March 02, 2015 based on code collected on Monday, March 02, 2015.

Re rasdaman: Analyzed on Monday, March 02, 2015 based on code collected on Monday, March 02, 2015.

Re OSGeo-Live: Analyzed on Monday, March 02, 2015 based on code collected on Monday, March 02, 2015.

Re gvsig-desktop-2: Analyzed on Monday, March 02, 2015 based on code collected on Saturday, February 28, 2015.

Re: opticks: Persistent error in fetch: svnsync: E210008: Error while replaying commit. Hmmm.

Thanks!

ssnow-blackduck about 9 years ago
 

Gerald,

Hopping on the Moose. Not sure what to suggest about Opticks - will consider it.

Thanks!

ssnow-blackduck about 9 years ago
 

Thanks a lot for your help, indeed almost all are in sync.

For Opticks specifically, I suppose that it comes from some code location definitions which are wrong, those starting with svn://, it should be replaced by http://. There is a message on the Opticks Code Location Administration page which mention that we may have to wait for 24 hours before asking question, so if I'm wrong in asking so soon, please tell me and forgive me.

I cannot fix the code location myself as I cannot edit from the admin page.

djay about 9 years ago
 

Gerald,

No worries. The problem is the fetch gets through many (18525) revisions in this case before giving up the ghost. We can try http:// transports but not sure if that will make any difference. Doesn't hurt to try, though. Standby.

Thanks!

ssnow-blackduck about 9 years ago
 

Gerald,

Re geomoose: Analyzed on Wednesday, March 04, 2015 based on code collected on Wednesday, March 04, 2015.

Re opticks: Unfortunately the https:// transport didn't make any change in the failure. I entered it as http:// but it changed it to https:// on me. Even so, it appears that it terminates at (in this case) r18525. It seemed to truncate some xml file in the middle of transmission and the error was svnsync: E130003: The XML response contains invalid XML. Looks as if we are bumping up against some timeout or limit that isn't very flexible. I'm going to try one other end-run: I'll try two enlistments one for trunk/future and one for branches/future. Then, if this works, you can add in any number of enlistments you like one-at-a-time. There must be some significant duplication of code between the various trees and it's probably distorting the figures significantly anyway but at least this way, you're counting all the latest commits. Let's see how it goes.

Thanks!

ssnow-blackduck about 9 years ago