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]
Hi,
Some of the source repository are blocked by failed jobs: https://www.openhub.net/p/petals/enlistments
At first I thought it was because of SSL certificate problems, but it is not the case, I double checked for each of them and they are working and using valid certificates.
Thanks!
Hi Victor;
While trying to fetch this Code Location:
URL: https://svn.petalslink.com/svnroot/trunk/product/dev/prod/petals/
Branch: /trunk/product/dev/prod/petals
Our code is generating the following error:
svn info --trust-server-cert --non-interactive -r 23913 --username='anonymous' --password='anonymous' --no-auth-cache 'https://svn.petalslink.com/svnroot/trunk0/dev/prod/petals/dev@23913' failed:
svn: E175013: Unable to connect to a repository at URL 'https://svn.petalslink.com/svnroot/trunk0/dev/prod/petals/dev'
svn: E175013: Access to '/svnroot/trunk0/dev/prod/petals/dev' forbidden
It looks like we're getting back a different path to files while fetching revision 23913.
Is there anyway you could take a look? And I apologize for the delay in getting back to you.
Thanks!
Hello,
Sorry I didn't see this message before…
I'm not exactly sure what is happening here, it seems there is something like a redirection, I guess using svn:externals, but I'm not able to pinpoint the exact source of this…
There is trunk0 directory anywhere, but well, I updated the credentials in the code locations and verified that with the new one it worked locally for this revision, and it seems to be the case :)
So now we just need for the retrieval to be triggered again!
Thanks