Hello.
It has been almost a 1 year since KDE 4 loocalization project enlistments were updated.
Could someone say what the problem is?
Thanks!
Alexander,
On the job. Will report back any progress tomorrow AM ET.
Thanks!
Alexander,
Having problems with both enlistments. Getting the following error from both either in the system logs or on my workstation: "svn: Compression of svndiff data failed".
This is not the error which shows on the system log for the initial fetch of the kde4 enlistment. That error is "Missing end tag for 'msg' (got "logentry") Line: -1 Position: -1 Last 80 unconsumed characters:" but I suspect they are related. Have tried both jobs in the last 17 hours with no luck.
An internet search points a finger at the server end and suggests that a reboot or re-start may be required to clear this error although you might expect that the reports would mount if this was a common error from that server's users.
It seems these enlistments are fairly large and complex (1.2 Gb for "support" and 1.3 million total commits for the subversion!) I hesitate to try to re-fetch this enlistment since it might take nearly forever to finish.
Perhaps you can make some discrete inquiries if there is any trouble brewing with the subversion or is it something else? In the meantime I'll check with management and see if they have seen this error before.
Thanks!
Alexander,
This is a little strange... It looks as if one of the enlistments I was researching last week has disappeared. No failed jobs show up now in the project (which is, I suppose, good...)
I will keep an eye on the project for a while anyway and follow the trends in case anything else goes wrong.
Thanks!
Alexander,
In the last day two initial fetches have failed. One is for the (main?) repository labelled "trunk" and the second labelled "branches". They both exhibit the same error: "Missing end tag for 'msg' (got "logentry") Line: -1 Position: -1 Last 80 unconsumed characters:"
The funny thing is that the same "trunk" repository is also present in 18 separate enlistments along language lines and all of those seem to be working. I suspect it has something to do with the size or complexity of the repositories.
Sorry I can't be more specific but I do have a call out to see if anybody on-staff has seen this behavior before.
Thanks!
Alexander,
You must have been doing considerable work on this issue while I was away. The main problem I found today was a "Connection closed unexpectedly" error on about a half-dozen enlistments. I pushed a little on these and they all cleared themselves.
Project should be up-to-date now.
Thanks!
Copyright
©
2013
Black Duck Software, Inc.
and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a
Creative Commons Attribution 3.0 Unported License
. Ohloh
®
and the Ohloh logo are trademarks of
Black Duck Software, Inc.
in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.