Since some time yesterday afternoon UTC, it’s no longer possible to create new enlistments. I’ve noticed that for git (some of the repos in some of my projects unfortunately switched to that thing), and other postings in the forums report it for cvs. I believe this is a bug on the Ohlol servers.
Please send specifics via e-mail and I'll track down what is happening... I'm sure you have my e-mail, but will send one just to be sure. It's hard to re-create the issue from this end unless I have the project and exact URL you want to add. It could be transient as well but I haven't heard about any maintenance going on in the last 24 hours that would prevent adding new enlistments. (Sometimes I'm the last to know!)
Will report back here with any news.
Sent the maiL 2 days ago, in case you didn't get it, tel me. Basically, added 2 git repos to mksh, one worked, a later one didn't, same server.
Posting with Mobile Internet Explorer on WinMo 6 because I'm at home, Firefox gets terminated by ProPolice, and the new Blackduck-Ohloh website makes Opera 9.2x segfault, and the other Browsers I have at home are Lynx, links+ and Dillo...
I could create a CVS enlistment today but still no git.
Even more specifically, I cannot add the Alt Linux repo, or its clone on eurynome, but I can add other repos sitting on eurynome.
I have received your email but my email to you was returned. I have enough info to start and if I find anything definite, I'll reply here.
It looks like repo
git://git.altlinux.org/srpms/m/mksh.git does not have a
master branch. Ohloh tries to read the master branch by default, and this is failing.
Are you specifying another branch name in the form, or letting it default to master?
Exactly, I was letting it default. Since my own cloning and ls-remote worked I never thought to look for this (might want to check that and display a different error message in that case). This new-fancy git stuff sure is weird. Thanks!
It appears to work now.
Was checking some older bugs to confirm their status and found a problem with one mksh job from 3 days ago. Rescheduled the "broken" enlistment which finished OK. Looks like a full update was run immediately after and has also finished OK.
Comments to this topic are now closed. Please create a new topic to get technical support.
The user who created the topic can reopen this topic at any time.