Re: Merge error with SVN 1.8.0
On Sun, Jun 23, 2013 at 7:38 PM, Alexey Neyman wrote: > On Sunday, June 23, 2013 07:20:50 PM Nico Kadel-Garcia wrote: > >> On Sun, Jun 23, 2013 at 3:56 PM, Alexey Neyman wrote: > >> > Hi, > >> > > >> > > >> > > >> > I've tried upgrading the client to SVN 1.8, and now see some strange >> > merge > >> > errors while reintegrating the branch. According to > >> > >> Did you delete the old RHEL 1.6.11 RPM, to avoid libraries lying > >> around and confusing you? Or binaries turning up in your "commit" > >> scripts due to inherited "PATH" that does not include the new version? > > > > Sorry for being unclear: I only upgraded the CLIENT, not the server. The > server still has 1.6.11. And yes, sorry for stating the obvious, the 1.7.10 > subversion RPM was removed when I installed 1.8.0. > > > >> To avoid the fun and games, I urge you to grab and test my newly >> minted Subversion 1.8.0 RPM building tools, at: >> https://github.com/nkadel/subversion-1.8.x-srpm > > Are you calling RPMs provided by WanDisco's "fun and games"? I think > Subversion developers employed by WanDisco might be somewhat insulted by > such judgment. Is there something wrong with RPMs from WanDisco that I must, > in your opinion, switch to your version? No, no, I missed that you were using WanDisco RPM's. (Not sure how I missed that, I do sometimes get interrupted doing my email.) I respect WanDisco's work and had no intent to insult them. And if you're using WanDisco, I'd seriously consider a commercial contract with them to take advantage of their multiple-master tools for mirroring Subversion repositories safely. That would actually help *fund* Subversion development. In fact If you can, I'd consider making a copy of the repository to another host and testing it with the Wandisco or another Subversion 1.8.0 *server*, not just client. >> I've also bundled a libserf SRPM building toolkit at: > >> https://github.com/nkadel/libserf-1.2.x-srpm > > Thanks. I thought that my original email indicated that we're using svn:// > protocol and thus serf is out of the equation. It's cool. I'm not suggesting you have to locally build or compile serf unless you care to build from my SRPM, It's a dependency for building a full Subversion 1.8.0 toolkit. If you feel like getting into the code yourself, you'll need something like it. In fact.. If you like playing with source and working with your own copies, > In other words: do you have anything relevant to say regarding the reported > issue, rather than advertising your work? I made a mistake about the source of your software, and did apologize. Since it's from Wandisco, and you're jumping to the bleeding edge with Subvesion 1.8.x on RHEL 6 based operating systems, why not contact them for commercial support?
svnsync 1.8.0 fails if htdigest authentication is used
Hi, After I upgraded to 1.8.0, svnsync process started to fail. I am using apache 2.2.3. I suspect it's really serf's problem (1.2.1), but nevertheless I had to revert back to 1.7.10. Is this a known limitation? Thanks, Vadym
Re: Merge error with SVN 1.8.0
On 24.06.2013 01:38, Alexey Neyman wrote: > > Are you calling RPMs provided by WanDisco's "fun and games"? I think > Subversion developers employed by WanDisco might be somewhat insulted > by such judgment. > Hmm I'd sooner be insulted by someone anticipating my reaction like that. :) Nobody's perfect. If you find a bug in WANdisco's binary packages, I for one would definitely like to know about it. -- Brane -- Branko Čibej | Director of Subversion WANdisco // Non-Stop Data e. br...@wandisco.com
Re: svnsync 1.8.0 fails if htdigest authentication is used
On Jun 30, 2013, at 07:06, Vadym Chepkov wrote: > After I upgraded to 1.8.0, svnsync process started to fail. I am using apache > 2.2.3. I suspect it's really serf's problem (1.2.1), but nevertheless I had > to revert back to 1.7.10. Is this a known limitation? You said you upgraded to 1.8.0. Was that the computer running svnsync, or the server serving the original repository, or both? What error message did you get?
Re: svnsync 1.8.0 fails if htdigest authentication is used
On Jun 30, 2013, at 2:18 PM, Ryan Schmidt wrote: > > On Jun 30, 2013, at 07:06, Vadym Chepkov wrote: > >> After I upgraded to 1.8.0, svnsync process started to fail. I am using >> apache 2.2.3. I suspect it's really serf's problem (1.2.1), but nevertheless >> I had to revert back to 1.7.10. Is this a known limitation? > > You said you upgraded to 1.8.0. Was that the computer running svnsync, or the > server serving the original repository, or both? > > What error message did you get? Both source and destination run under Linux. Authentication fails, I see 401 in the apache's access log.
Re: svnpubsub dependcy problem building RPM's for Subverssion 1.8.0
On Tue, Jun 25, 2013 at 9:40 AM, Daniel Shahaf wrote: > On Mon, Jun 24, 2013 at 03:40:44PM -0400, Nico Kadel-Garcia wrote: >> The normal way to handle changing deployment environments is with an >> actual configuration or deployment tool, such as autoconf, that sets >> the path to the locally detected python and uses *that*. > > The detected Python (if any) is available in Makefile as $(PYTHON). > > (I have nothing to say to the rest that wasn't already said somewhere on this > thread (perhaps on the dev@ part of it).) Good point. Setting it in svnpubsub would then mean *generating* the files to be installed form the existing *.py files. Ideall for that, they'd be named "script.py.in" instead of "script.py" and built during the "make" process. But for now, unless the author of the svnpubsub tools cares to rewrite them, I think the wrapper script in the SRPM I've written will cover the RHEL setups.
