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 Update
hello, whenever possible could a admin take a look at: EasyBSD ... it seems that svn updates aren't taking place.
How often does the site check svn for new commits ?
Thanks
- jewles
Greetings Jewles,
Here are the commits we're aware of. Does it seem correct or just out of date?
We try to update projects daily however we are currently running a few weeks behind at this point. We're catching up and can manually poke any project you'd like. Would you like a refresh right now or are you referring to a different issue?
Hello Jason,
Sorry if I wasn't clear in my initial post. I am after two things. First of course is if it is possible to manually update the svn again please. The latest revision is 13 and not 5.
<~/fbsd-dev/easybsd> svn up
At revision 13.
And the second which is mostly answered, the schedule for when updates occure. From what I understand from your post, they aren't done manually? If this is true, how come? Thanks.
Actually, I've just had to redo my whole SVN repository... If you could redo the thing... I have a feeling it will mess up otherwise.
hi Julian,
I tried redoing it from scratch but ran into a problem. I'm not sure what it is yet but unfortunately it will have to wait until morning (here in Seattle, anyway). Sorry for the delay.
No problem... If you guys need help... I don't have much going on... :) I am a okay admin! :)
Now I feel the delay, whole day has come and gone.
lol, patience amigo :P
Hi Julian,
There are some serious problems in this Subversion repository. Have you used admin tools to edit this repository? Did it change substantially after we already started downloading it?
The log appears completely corrupted -- revision numbers appear out of order. For instance, in the log, I see revision 221, then revision 4, then revision 220, then revision 3, then a blank revision which will certainly break our parser, then revision 219.
Also, even though we specifically request only the /trunk log, we see some events inside /branches in commit 222.
Let us know when you get this repository sorted, and we'll dump what we've got so far and try again.
Yes, actually I did. I was going to post the changes but forgot to mention it in my last post. EasyBSD is a continuation of INSTALL7... So my dev team redid the svn repository. And instructed me to delete and add the svn info back. I didn't think it would work... And I'm correct... But this was way after the svn wasn't working on this site anyway... And was still waiting for a response from an admin.
As far as I'm aware the SVN is perfect atm. My team and I have done several tests... and updates.
my enlistment is still reading failed. can a admin flush the current svn information, and redownload the new.
Thanks
Hi Julian,
The Subversion is still corrupted. You may be able to check out and check in to this repository, but the historical information is confused.
Try this:
svn log svn://core.netstable.com/easybsd/trunk | grep -E -e'^r[0-9]+'
You will readily see that revisions 3 and 4 are out of order. This happens with either URL.
If you view the full log, you will also find blank revisions after 3 and 4.
Also, revisions 3 and 4 cannot be checked out:
$ svn co -r3 svn://core.netstable.com/easybsd/trunk@3
svn: URL 'svn://core.netstable.com/easybsd/trunk' doesn't exist
Until the log comes back correctly sequenced, and unless all revisions in the log can be checked out, the Ohloh downloader is going to fail.
I don't know the history of this repository, and I don't do much actual Subversion administration, so I can't really give much help on how to fix this. Perhaps someone else reading this thread has an idea....
Alright. This time I promises everything is okay. :) I reverted back to the last working revision which was r218. Then I manually copied over changes since then... as far as I can see the revisions are now in perfect working order... below are a list of the last 15. now, i just noticed something 'weird' the order is perfect... now what if it skips a few revisions... ie i see a few missing revisions no r215, no r217:r219.... thanks again for the help Robin...
<~/fbsd-dev/easybsd> svn log svn://core.netstable.com/easybsd/trunk | grep -E -e'^r[0-9]+' | more
r224 | julian | 2007-08-30 05:39:45 -0400 (Thu, 30 Aug 2007) | 2 lines
r223 | julian | 2007-08-30 05:39:13 -0400 (Thu, 30 Aug 2007) | 2 lines
r222 | julian | 2007-08-30 05:36:34 -0400 (Thu, 30 Aug 2007) | 2 lines
r221 | julian | 2007-08-30 05:32:46 -0400 (Thu, 30 Aug 2007) | 1 line
r220 | julian | 2007-08-30 05:29:50 -0400 (Thu, 30 Aug 2007) | 1 line
r216 | julian | 2007-07-22 09:27:39 -0400 (Sun, 22 Jul 2007) | 1 line
r214 | julian | 2007-07-17 10:36:57 -0400 (Tue, 17 Jul 2007) | 2 lines
r212 | julian | 2007-07-14 13:03:10 -0400 (Sat, 14 Jul 2007) | 2 lines
r211 | julian | 2007-07-14 12:20:40 -0400 (Sat, 14 Jul 2007) | 1 line
r210 | julian | 2007-07-14 12:18:23 -0400 (Sat, 14 Jul 2007) | 1 line
r206 | julian | 2007-07-14 08:31:54 -0400 (Sat, 14 Jul 2007) | 1 line
r202 | julian | 2007-07-14 06:41:05 -0400 (Sat, 14 Jul 2007) | 1 line
r201 | julian | 2007-07-14 05:58:39 -0400 (Sat, 14 Jul 2007) | 1 line
r200 | julian | 2007-07-14 05:34:02 -0400 (Sat, 14 Jul 2007) | 1 line
r199 | julian | 2007-07-14 01:51:12 -0400 (Sat, 14 Jul 2007) | 1 line
Is it possible that regardless if svn repository is perfect or not that my current svn enlistment be dumped and started over ? thanks
Hi Julian,
Good news -- the download succeeded. I did a clean download, and everything is looking good from our end.
Bad news -- you will undoubtedly notice that our history doesn't show anything before July 14. I guess it's ironic that after all of this trouble you have now encountered a limitation in our Subversion importer. If you rename your trunk directory (in your case, the name changed from /install7 to /trunk), our import stops at the point where the name changed. A lot of folks (including me) are not crazy about this.
hmm... well i'm pretty happy all is well now...
I am curious thou if there are any plans on fixing the cause of this bug/error. is it truly my repository, and if so what could I do to either 1. fix it so this site can download/view all logs 2. make sure I have no further problems with SVN... (obv, not touching it is one way... )
Also, I am really interested in helping out if possible. I've read on several posts that you are behind on commit updating... and whatnot... have nothing but time. (minus of course when I actually get around to doing some updates/coding on my project).... If you are only wanting to keep the dev team small, thats understandable... :)
Thanks again for the help... Julian
...
Hi Julian,
Yes, there are plans to fix this Subversion import problem, but it could be a while before we have time to do it. At this point there's not much you can do on your end; it's strictly a limitation on our end.
In terms of being behind on updates, that's mostly a systems administration issue [which I am sinking endless time into lately], and unless you can drop ship me a half dozen new servers I think we're on our own here.
But we are thinking seriously about ways to get help from the community in terms of Ohloh features, specifically supporting more languages and more source control systems. Again, this is something that will take us some time to get organized, but stay posted.
Thanks,
Robin