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]
FreeBSD project stuck
https://www.ohloh.net/projects/freebsd/enlistments
Is this repository just too big for Ohloh to cope with?
Same for MirBSD… https://www.ohloh.net/projects/mirbsd
MirPorts worked though, from the same server, although that’s a lot more (smaller) files.
Hi Aristedes,
Yes, this is a pretty large repository. Does the repository support svnsync? If so, we can try an alternative download method which is much faster and might work for us.
Thorsten,
We are unable to fetch the rlog for this repository. There's a consistent problem with one file in particular:
$ cvsnt -d :pserver:peed:[email protected]:/peed/repos/new rlog -b -r1: 'alles/repository/src/gnu/usr.bin/perl/Attic/mv-if-diff'
RCS file: /peed/repos/new/alles/repository/src/gnu/usr.bin/perl/Attic/mv-if-diff,v
head: 1.2
branch:
locks:
access list:
Terminated with fatal signal 11
Any clues what this might be? Any chance that this can be repaired? Without the rlog our importer can't function.
Thanks,
Robin
This is very interesting; a semicolon was missing in that file (rlog from GNU RCS discovered it, GNU CVS just segfaults).
Thanks for the hint, it should be fixed now (works for me). If there are further problems, feel free to contact me back, even by eMail.
Hi Thorsten,
We are still having problems. This rlog...
cvsnt -d :pserver:peed:[email protected]:/peed/repos/old rlog altes
...contains invalid timestamps, such as 2004-00-11 23:20:44.
There are a variety of bad timestamps like this, all of them with a 00 in the month column. Our system can't parse these.
Very interesting. Some version of CVS must have not been Y2038 (64-bit time_t) safe… fixed in the comma-v files, please reschedule. Thanks!
Robin,
Svnsync does not require any special server-side support or configuration - you can svnsync any svn 1.4 and newer repo that you can access. The FreeBSD repo is currently at 1.5.
