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
info@openhub.net
updating kdebase failed
Hi
It seems that updating svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase failed (used in project KDE)
This also prevents ohloh updating the code analasys.
By the way: Is it possible to use jokers in repository names?
Say svn://anonsvn.kde.org/home/kde/trunk/l10n-kde4/*/messages?
This would speed up updating the reports for KDE 4 localisation.
Regards
Kristof
Hi Kristof,
It looks like we encountered a very strange corruption problem with one of the revisions. I've scheduled a new attempt to see if it's a real problem in the repository, or simply one of those things
. If the problem doesn't go away I'll investigate and report back.
And no, sorry, we don't support wildcard names, although given the number of repositories that some projects are using, that certainly would be helpful.
Thanks a lot!
Another question: What do you do when you update repository, do you re-download it, or do you run svn update?
Hi Kristof,
It looks like there is something funny going on in one of the revisions of this repository:
~$ svn checkout -r 841619 'svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase@841619' kdebase
svn: In directory 'kdebase/workspace/cursors/src/theme-norway'
svn: 'kdebase/workspace/cursors/src/theme-norway/.svn/tmp/text-base/CMakeLists.txt.svn-base' has unsupported special file type 'add_theme(${color}'
This error prevents us from completing the update. Any chance that this can be repaired?
It's possible that we might be able to simply skip some revisions, if you can figure out which revision removes the error.
To answer your other question, our updates are incremental. We individually check out each new revision and compute deltas on each.
With some servers, we are able to use svnsync, which of course is much faster for us, but when the server doesn't support svnsync we have to fall back on sequential checkouts.
Hmm, I'm not at all sure -- that's beyond my Subversion expertise.
Are you able to reproduce the error?
With the revision you used I also get an error, but from r841630 on, evereything works fine.
So if it's possible, skip al revision earlier than then.
By the way, kdelibs (same project) failed on counting lines of source code, can you fix that?
Thanks
Kristof
Hi Kristof,
I am attempting a manual revision skip, but this is pretty difficult to do and it doesn't always work out correctly. It's also only a temporary fix, since if Ohloh ever needs to re-create the report, then the fix will need to be applied again.
The line count failures have been rescheduled.
I'll be tinkering with this throughout the day, hopefully we'll get some positive results.
Thanks,
Robin