Setting LC_ALL=C does not work either. Wonder why it works for v1.7 but not for v1.6. Again, I'm getting "svn: Compression of svndiff data failed" when executing "svn co svn://path/to/repo/prj working_directory". But if I do a "svn co file:///...." then it's okay for v1.6.
On Tue, Dec 20, 2011 at 9:38 PM, <phillip...@gmail.com> wrote: > Please forgive me but how do you install the v1.7 libraries on top of > v1.6. Is it basically performing the compilation of v1.7 and installing it > over the v1.6 directory location? > > On Tue, Dec 20, 2011 at 6:11 PM, Daniel Shahaf <d...@daniel.shahaf.name>wrote: > >> please reply to all so so replies go to the list >> >> phillip...@gmail.com wrote on Tue, Dec 20, 2011 at 18:00:07 -0500: >> > Hi Daniel, >> > >> > Thanks for your response. I'm using a middleware product called >> > webMethods. Not sure if their product support the latest stable >> release of >> > subversion v1.7 but with v1.6, the product works well when doing api >> calls >> > to check in/out. >> > >> >> Well, you could try installing the 1.7 shared libraries on top of the >> 1.6 ones; should just work >> >> > Anyways, by setting LC_ALL=C environment variable (I'm running AIX >> server), >> > what exactly does that do? Strange that I don't have to set this when >> > running v1.7. >> > >> >> Force output to be in English if it's in some other language (via >> gettext library) >> >> > On Tue, Dec 20, 2011 at 5:35 PM, Daniel Shahaf >> > <d...@daniel.shahaf.name>wrote: >> >> >> > >> > > Phil wrote on Tue, Dec 20, 2011 at 17:22:52 -0500: >> > > > Whenever I use "svn://" protocol to checkout numerous files at one >> time, >> > > I >> > > > get the error "svn: compression svndiff failed data" at some point. >> > > >> > > (You either misquote the message or mistranslate it. In the latter >> > > case, set LC_ALL=C in your environment.) >> > > >> > > > However, this doesn't occure when using "file://" protocol. Does >> anyone >> > > > know how to resolve this with svn v1.6? This doesn't occur with svn >> v1.7 >> > > > but I prefer to use v1.6 because it works or integrate well with >> another >> > > > product. >> > > > >> > > >> > > I'm curious about the latter part. What products do you have that >> work >> > > with 1.6 and not with 1.7? We publish stable public APIs exactly to >> > > prevent people from ending up in that state. >> > > >> > > > -Phillip >> > > >> > > Daniel >> > > (I don't have any specific insight on your actual error though, >> sorry.) >> > > >> > >> > >> > >> > -- >> > Regards, >> > Phillip >> > >> > ************************************************ >> > This e-mail, and any attachments thereto, is intended only for use by >> the >> > addressee(s) named herein and may contain legally privileged and/or >> > confidential information. If you are not the intended recipient of this >> > e-mail (or the person responsible for delivering this documentto the >> > intended recipient), you are hereby notified that any dissemination, >> > distribution, printing or coping of this e-mail, and anyattachment >> thereto, >> > is strictly prohibited. If you have received this e-mail in error, >> please >> > respond to the individual sending the message, and permanently delete >> the >> > original and any copy of any e-mail and printout thereof. >> > ************************************************ >> > > > > -- > Regards, > Phillip > > ************************************************ > This e-mail, and any attachments thereto, is intended only for use by the > addressee(s) named herein and may contain legally privileged and/or > confidential information. If you are not the intended recipient of this > e-mail (or the person responsible for delivering this documentto the > intended recipient), you are hereby notified that any dissemination, > distribution, printing or coping of this e-mail, and anyattachment thereto, > is strictly prohibited. If you have received this e-mail in error, please > respond to the individual sending the message, and permanently delete the > original and any copy of any e-mail and printout thereof. > ************************************************ >
