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]

svn short history

Hi,
I noticed that the project 'beagle' is showing Short source control history (8 months) - however the svn history shows activity since 2004 (e.g. using the viewcvs interface http://svn.gnome.org/viewcvs/beagle/trunk/beagle/tools/Query.cs). Any clue what is going wrong ?

Thanks.

dbera over 18 years ago
 

Hi dbera,

We are unable to download the CVS repository for beagle, so the results are from SVN, which shows 8 months of history. The error we're running into with CVS is:

$ cvsnt -d :pserver:anonymous:@anoncvs-i-know-i-should-use-svn.gnome.org:/cvs/gnome rlog -b -r1: 'beagle'

cvs rlog: Logging beagle

cvs rlog: failed to create lock directory for '/cvs/gnome/beagle' (/cvs/gnome/beagle/#cvs.lock): Read-only file system

cvs rlog: failed to obtain dir lock in repository '/cvs/gnome/beagle'

Andy Verprauskus over 18 years ago
 

Hi Andy,
Thanks for the reply. Yeah, I know there is some problem with the anon cvs server of gnome, but I was referring to the history from svn. If I check the web-interface of the svn repository or the anon svn checkout (using svn log), I get history from 2004. E.g. there is a file called HACKING as beagle/trunk/beagle/HACKING. Doing svn log gives
$ svn log HACKING | grep lines
r3244 | dbera | 2007-01-09 20:27:10 -0500 (Tue, 09 Jan 2007) | 5 lines
r3170 | joeshaw | 2006-12-30 11:03:51 -0500 (Sat, 30 Dec 2006) | 4 lines
r3168 | joeshaw | 2006-12-30 11:02:09 -0500 (Sat, 30 Dec 2006) | 2 lines
r3156 | joeshaw | 2006-12-20 11:19:31 -0500 (Wed, 20 Dec 2006) | 2 lines
r2916 | joeshaw | 2006-10-16 13:16:28 -0400 (Mon, 16 Oct 2006) | 2 lines
r2796 | rml | 2006-09-03 21:36:19 -0400 (Sun, 03 Sep 2006) | 9 lines
r2649 | joeshaw | 2006-06-14 13:31:12 -0400 (Wed, 14 Jun 2006) | 2 lines
r2460 | joeshaw | 2006-03-27 18:47:55 -0500 (Mon, 27 Mar 2006) | 2 lines
r1958 | dbera | 2005-10-06 17:33:21 -0400 (Thu, 06 Oct 2005) | 2 lines
r1030 | dsd | 2005-03-21 14:41:42 -0500 (Mon, 21 Mar 2005) | 2 lines
r557 | trow | 2004-11-17 02:24:48 -0500 (Wed, 17 Nov 2004) | 11 lines
r118 | trow | 2004-06-20 17:23:24 -0400 (Sun, 20 Jun 2004) | 2 lines
r95 | trow | 2004-06-07 03:44:49 -0400 (Mon, 07 Jun 2004) | 2 lines
r86 | trow | 2004-06-03 02:44:05 -0400 (Thu, 03 Jun 2004) | 3 lines
r19 | trow | 2004-05-03 15:50:32 -0400 (Mon, 03 May 2004) | 2 lines
r2 | trow | 2004-04-29 18:53:52 -0400 (Thu, 29 Apr 2004) | 2 lines

I was wondering why isn't ohloh able to retrieve these history ? Could it be that becase the cvs download failed, even the svn history is getting messed up ?

dbera over 18 years ago
 

We only see history back to December 2006 because we check history project wide by doing a command that's basically:

svn log --stop-on-copy http://svn.gnome.org/svn/beagle/trunk

This is because we're looking for changes which we can download and parse for language, comments, lines of code, etc. HACKING doesn't exist as a downloadable resource until the project-wide history starts, in December 2006. For instance, if you try to get the HACKING from it's first checkin with

svn update -r 2 HACKING

you won't receive a file. This is probably because HACKING was renamed, the directory it was in was renamed, or it was branched. For a number of reasons which Robin has explained in more depth in other posts, we are unable to follow branches in SVN currently.

Andy Verprauskus over 18 years ago
 

Aha ... you do a --stop-on-copy. Thats why the old copied history is not getting reflected. I guess I will have to live with this unless ... unless you guys have some way of doing
$ svn log --stop-on-copy -r 3167:1 http://svn.gnome.org/svn/beagle/trunk
(sadly, at 3168 trunk was moved to another branch which was later moved back to trunk)

dbera over 18 years ago