On Thursday 07 May 2009 19:11:38 C. Michael Pilato wrote:
> > TODO: File a Subversion issue about the problem, noting the fix in APR,
> > but devising a workaround for folks that can't easily get a new APR
> > release. I suspect this will have a little something to do with not
> > using
> > apr_brigade_vprintf() at all for the large property values, but using
> > apr_brigade_write() directly instead.
> Okay, I never got around to filing the issue, but the APR fix is done, and
> now trunk uses the workaround of _write() instead of _vprintf() for the
> large base64 property block now (with a backport recommended for 1.6.x).
Thank you for following up on this. I have been distracted from the topic by
other issues, but I will try the workaround. KDE's SVN is, unfortunately, not
publicly accessible -- people noticed that earlier in the thread. Getting SVN
access is a matter of filling in a webform and waiting a few hours, but still
I actually hit a totally different issue while svnsyncing KDE's repo's again
(now with SVN 1.6): revisions with inconsistent line endings in the log
message, way back in r.300000 or so. Those had not previously been an issue,
but my svnsync stranded on that long before hitting the problematic-in-this-
thread revision of 940000-odd.
Received on 2009-05-08 11:24:28 CEST