[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 'Could not get next bucket brigade' error

From: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 18 Mar 2011 15:50:23 +0100

On Fri, Mar 18, 2011 at 10:40:34AM -0400, Nico Kadel-Garcia wrote:
> Rechecking my test environment, 1.6.16 builds well enough on RHEL
> 5/CentOS 5 with just the version change. RHEL 6 is a *disaster*,
> partly due swig integration. (RHEL 6 finally has a recent enough swig
> and sqlite not to need the separate tarballs, but that code needs
> graceful management.)
>
> The internal ".spec" structure in
> http://svn.apache.org/repos/asf/subversion/trunk/packages/rpm/ is also
> *very* dangerous. It replaces the user's own .rpmmacros, without
> warning and without making a backup. This is hideous behavior. I'll
> send along some patches for that ASAP.

I agree that's hideous.
Patches to the packages are welcome.
The last serious update seems to have been in 2009.

But have you looked at red hat's source RPMs? If RPMforge packages could
be based on those, we might as well delete our own packages/rpm/ directory.
Build scripts for most Subversion packages these days are maintained elsewhere.
Received on 2011-03-18 15:51:06 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.