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]
2 years since last project update?
I have 2 years since I wonder what could be wrong with ohloh that left my project behind... I also thought the ohloh service was going down.
Now, I'm glad it didn't happen, but is there anyone to put phpmychat on the update list please? Thank you.
https://www.ohloh.net/p/phpmychat
PS: Do I have to ask for this after each commit? Shouldn't be an automatic process?
Oh... Ohloh reports on my last commit day that I left the project in 2009! That never happen. It might be the moment sourceforge made the big switch to the new upload system, I don't know, but I never left the project and made some 200 more commits in the last 2 years. Please correct this as the info is very inaccurate...
Thank you!
Ciprian,
The process should be automatic (when all goes well) but you have been bitten by a troublesome bug that we have been trying to eradicate for a while. You will see on the enlistments page that one enlistment (Failed about 1 year ago.) while the others haven't been updated for 6 months. I will manually reschedule the one that's hung and the rest will update automatically as they should.
I'll report back once everything is updated.
Thanks!
Ciprian,
The hung update is continuing to hang... I have run an re-fetch on it with the same results. I have escalated the problem to management to get a practiced eye to look at the problem. I'm suspicious, though, since I notice there are two enlistments here that are very similar: one CVS module name in all lower case phpmychat
and one in mixed case phpMyChat
. Is this causing confusion somewhere? I will leave it to the experts for a while but if things don't improve in a couple of days, you can do history/undo for the enlistment that's causing trouble and let the rest of the enlistments get up-to-date and get a new analysis.
I'll let you know here if I hear anything about the problem.
Thanks!
Thank you.
Just a note: I've never changed anything on the enlistments since the first update worked... then it worked fine for a while... until suddenly had stopped. But i didn't change a thing, not even the caps. Indeed phpmychat or phpMyChat refer to the same project (second would be the official name), but if needed, i can correct the spelling caps as per your directions. Thank you again for looking into it.
Ciprian,
The spelling issue is only on our side... we should be able to distinguish two truly separate enlistments with the only difference being the capitalization on the CVS module name but there may have been an error that has crept in. It's only a suspicion anyway. There could be a whole different explanation for the problem. I'll let them do their thing and we'll see. I have gotten you a partial update of all the other enlistments.
Thanks!
Ciprian,
The answer is:
"This is an empty repo.
cvsnt -d :pserver:anonymous:@phpmychat.cvs.sourceforge.net:/cvsroot/phpmychat rlog phpMyChat
generates empty respone.
This enlistment should simply be removed from the project."
So, funny thing is, the web interface agrees - I'm surprised I didn't check it yesterday (or did I...)
I'm just going to disable that enlistment and let the updates continue.
Thanks!
Ran history/undo on the enlistment just like I did yesterday. Update of the remaining enlistments is now finished.
Analysis page is now at May 17 2012 and last commit is at 2012-05-10.
Please be sure you remind me here if the project stalls again.
Thanks!
Thank you, it seems it worked fine. I will keep reminding if it stalls.
Is there anything else should I still fix/add/delete about the enlistment/enlistments?
Ciprian,
Only thing I can see is that there must be a fair amount of duplication with the remaining enlistments. Depending on whether you want to focus on historical data and retain that history or whether you want a fairer portrait of the project at this time, you may want to retain the same enlistments or concentrate on the repository where the majority of the development effort is seen. Managers seem split between the historical record and current development. Some decide to have two projects - one as you have it currently and a second just to monitor the current state of the active enlistment.
Thanks!