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]
kdebase/runtime failed 5 month ago
Hi,
svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase/runtime
failed in the KDE project 5 month ago and some others too. All the other projects completed 2 days ago. Could you please enable them again?
Thanks!
-- andreas
Hi Andreas,
Our parser is having a fatal problem with this:
~$ svn log -r 997199:997190 svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase/runtime
------------------------------------------------------------------------
r997199 | sukharev | 2009-07-15 06:59:28 -0700 (Wed, 15 Jul 2009) | 1 line
?\129?\195?\189?\212
------------------------------------------------------------------------
Does this look any better on your end?
We actually use the xml version of the log, but it's not encoded any better than the plain text version.
It's possible that this is an encoding problem on our end, but I suspect that the problem is in the repository data itself.
There may be workarounds, but in the near term this is a breaking issue for our code.
Thanks,
Robin
Hi Robin,
no it doesn't. I see the same here. Just the web output looks different.
http://websvn.kde.org/?view=rev&revision=997199
Is it possible to skip this commit?
Thanks!
-- andreas
Hey Robin,
we have fixed the commit.
svn log -r 997199 svn+ssh://[email protected]/home/kde/trunk/KDE/kdebase/runtime
r997199 | sukharev | 2009-07-15 15:59:28 +0200 (Wed, 15 Jul 2009) | 2 lines
empty log
Could you restart the parser?
Thanks,
-- andreas
Really? I see the exact same log output as before.
~$ svn log -r 997199 svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase/runtime
------------------------------------------------------------------------
r997199 | sukharev | 2009-07-15 06:59:28 -0700 (Wed, 15 Jul 2009) | 1 line
?\129?\195?\189?\212
------------------------------------------------------------------------
I rescheduled the job, and it failed in the same way as before.
Am I missing something obvious here?
Arg, it is not on the mirror yet. I have to talk to the mirror admin.
The changes are on anonsvn.kde.org now too.
Sorry, Andreas, I still get the same result as before :-(.
Hi!
At least in the web interface, only kdegames svn update is broken recently. Could you post this svn error?
Another (newbie?) question: Does Removing a problematic enlistment help the update process?
Thanks =)
Hi Anselmo,
Our Subversion log parser is choking on revision 952636:
~$ svn log -r 952636 svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames@952636
------------------------------------------------------------------------
r952636 | swilson | 2009-04-12 05:01:24 -0700 (Sun, 12 Apr 2009) | 1 line
I?\1371?\192H?\139\H?\139l$L?\139d$L?\139l$ L?\139t$(L?\139|$0H?\131?\1968?\195I?\141T$ ?\233q?\254?\255?\255M?\133?\246?\184
------------------------------------------------------------------------
And to answer your question: yes -- removing a problematic enlistment from Ohloh will allow the project update to go through. If any enlistment cannot be updated, the entire project becomes blocked.
Thanks,
Robin
Removing the problematic enlistment allowed the update. Now I'll check with kdegames and/or sysadmins to fix that commit. Thanks! =)
The above problem in kdebase is fixed in the main repository, but the changes haven't been propagated to the mirror like anonsvn.kde.org. Could you please ask sysadmin to do a sync with the mirrors too?
The problem in kdebase seems solved in anonsvn too. I'll report the one in kdegames.
The problem in KDE base isn't solved, there is still the crippled log on the anonsvn server. It needs a full synchronize to get it working.