No, it was our fault. I finally found a rule blocking port 443 from 207.115.86.106 and a reverse DNS lookup revealed the host name sudan.ohloh.net. I guess that is your machine. I'm very sorry for ... [More] that! I didn't know and it took me quite some time to find it (wasn't in the default table). I'm still trying to find out why that ended up in our firewall configuration... Thanks a lot for your fast help!!! Best regards, Marco :-) [Less]

I have already taken a look into the firewall before, but didn't see any block at all for port 443. Could you please tell me an IP from which it does not work? I could grep then for it...

Thanks for trying it again! I hope, too, we'll be luckier now.

Hi Robin, thanks a lot for taking care of this problem. I just saw that it is in failed state again - maybe there are some network problems? I have no trouble to browse ... [More] https://svn.jfire.org/svn/main/trunk from where I am right now (South-East-Asia), thus I assume the problem is a regional network problem (or international peering between Europe and US). Can you connect to our SVN repository with an ordinary browser, right now? Best regards, Marco :-) [Less]

Hello *, according to https://www.ohloh.net/p/jfire/enlistments the main repository wasn't successfully queried for 2 months already. Could you please fix it? Thanks a lot in advance! Best regards, Marco :-)

Hi Robin, thanks a lot for the elaborate response. It would be really cool, if you could replace the current enlistment by the SVN root. I doubt that it will cause significant load to your servers ... [More] , because the whole library currently has less than 2000 lines of code ;-) We're at the moment doing some major refactorings and therefore might need a branch (we didn't create it yet - still working on trunk). If we temporarily need a branch, we'll very likely delete this work-in-progress branch when the refactorings are done. If we find out later, that branches are regularly used, we can still delete the current root-enlistment and register trunk instead. Till then trunk is aged and the project doesn't look as if it was created yesterday ;-) Additionally, till then ohloh.net will probably have become more mature and likely the current issues have been fixed... Best regards, Marco :-) [Less]

Hello *, today, I added an enlistment for the project Mime Type Detection Utility. Since the project was directly in the root of the SVN repository and we're now needing branches, I created a "trunk" ... [More] folder and moved the project there. Thus, the source code history is now 1 day long (instead of 2 years) and all the code is listed as being mine (even though it's not much code, it should be assigned to the right contributors). In order to solve this problem, I deleted the enlistment https://mime-util.svn.sourceforge.net/svnroot/mime-util/trunk and wanted to add the base URL https://mime-util.svn.sourceforge.net/svnroot/mime-util. This, however, didn't work. Whenever I tried to re-add the enlistment, ohloh.net added the URL with "trunk"-suffix (even though I specified another URL). After my last try, it even automatically added "MimeUtil" (i.e. a sub-project under "trunk") instead of the "trunk" base URL. Is there a way to get the old repository information, which was https://mime-util.svn.sourceforge.net/svnroot/mime-util/MimeUtil into ohloh.net together with the current and future information from https://mime-util.svn.sourceforge.net/svnroot/mime-util/trunk (all subdirectories - not only "MimeUtil")? Best regards, Marco :-) [Less]

Hello Robin, thanks a lot for your fast reaction and your help! It seems to have worked fine. All enlistments are updated successfully. Best regards, Marco :-)

Hello *, the download of one enlistment in each of the 2 projects failed and the other enlistments have been updated 13 days ago: https://www.ohloh.net/projects/pdfviewer/enlistments ... [More] https://www.ohloh.net/projects/jfire/enlistments Could you please take a look? Thanks a lot! Best regards, Marco ;-) [Less]

Hello Robin, thanks a lot! I just took a look at the enlistments and all of them have been successfully updated within the last 10 hours. Best regards, Marco :-)