You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Ben Reser <be...@reser.org> on 2004/04/02 08:41:11 UTC
Re: Multiple APR versions are a problem?
On Wed, Mar 31, 2004 at 09:08:08PM +0100, Barry Scott wrote:
> I've been deploying subversion and noticing problems
> that have APR incompatibility at there root.
>
> Mandrake 9.2 runs httpd 2.0.47 and uses an old libapr.
> Its not possible to install the svn client without
> replacing the httpd because of sharing libapr.
Using my packages can solve this for you. I have all the dependencies
solved for you. You can find my packages here:
http://mirror.brain.org/linux/breser/mandrake/
Details on how to add my page as a urpmi source are here:
http://ben.reser.org/mandrake/breser/
> In our case we don't want to replace the httpd, so
> it limits svn deployment.
Why? If you're worried about support, I can assure you that my Apache
packages will be kept up to date with security fixes. One of the
machines that serves stuff for the Mandrake security team is running
those packages.
If you find bugs in my packages, I want to know about it. I'll be happy
to fix them, I'm running them on the platforms I have up (including
Mandrake 9.2).
> On windows each kit that installs the svn files, tsvn,
> subversion and pysvn will all need to set the same
> environment variable APR_ICONV_PATH. Why can't the svn
> code find its iconv files without the use of the env
> var?
I'll have to defer to one of the Windows guys about this.
> Is this just a temporary issue or is churn in apr going
> to make it ongoing problem?
APR isn't at 1.0 yet. As a result they're still finding and fixing
problems...
--
Ben Reser <be...@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Multiple APR versions are a problem?
Posted by Ben Reser <be...@reser.org>.
On Sat, Apr 03, 2004 at 02:39:06PM -0500, John Peacock wrote:
> That's the basic problem with building RPM's in parallel to a distro; even
> the most radical distro's are very conservative about updating packages.
Mandrake almost always has the latest version unless there's a reason
not to. They're not conservative generally in that regard. That's one
thing a lot of people like about them.
> Perhaps if you reminded the Mandrake cooker drivers that BDB4.1 will cause
> corruption with Subversion, you can get a ruling on adding a parallel
> BDB4.2 RPM. After all, if they intend to release Subversion in the
> mainline, they should get the recommended BDB into Cooker as soon as
> possible...
Nope subversion isn't in main, it's not really my call if it will end up
there. It's kinda difficult to ask a main package to change versions to
support a contrib package...
I could probably just add the bdb 4.2 RPM myself without asking for a
ruling. But I don't really want to maintain it. I've already got
enough packages that I maintain...
--
Ben Reser <be...@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Multiple APR versions are a problem?
Posted by John Peacock <jp...@rowman.com>.
Ben Reser wrote:
>>heard of _any_ problem with 4.2.
>
>
> Typo. I meant 4.1.
That makes me feel better. ;~)
> I'm hesitent to put out bdb 4.2 packages because Mandrake hasn't
> upgraded even in cooker. I really don't know what their reasoning is.
> But I have to keep my packages building on cooker. I'm not really in a
> position where I get to decide what bdb version they have.
That's the basic problem with building RPM's in parallel to a distro; even the
most radical distro's are very conservative about updating packages. Perhaps if
you reminded the Mandrake cooker drivers that BDB4.1 will cause corruption with
Subversion, you can get a ruling on adding a parallel BDB4.2 RPM. After all, if
they intend to release Subversion in the mainline, they should get the
recommended BDB into Cooker as soon as possible...
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Multiple APR versions are a problem?
Posted by Ben Reser <be...@reser.org>.
On Sat, Apr 03, 2004 at 01:23:12PM -0500, John Peacock wrote:
> Ben Reser wrote: >>You are using BDB 4.1.?? I think using 4.2.?? is
> more stable.
> >
> >
> >There are problems with 4.2 in some certain circumstances. I simply
> >don't think these circumstances warrant replacing the system bdb4.
>
> There are known bad problems with 4.1 on multiple platforms under
> repeatable circumstances with Subversion. This is the first I have
> heard of _any_ problem with 4.2.
Typo. I meant 4.1.
> In addition, there is no reason to replace the system bdb4 in order to
> use 4.2. Could you document what problems led you to this somewhat
> suprising change in accepted policy?
I'm hesitent to put out bdb 4.2 packages because Mandrake hasn't
upgraded even in cooker. I really don't know what their reasoning is.
But I have to keep my packages building on cooker. I'm not really in a
position where I get to decide what bdb version they have.
Obviously anyone that needs a bdb4.2 linked subversion can do so simply
by installing it and rebulding my packages against it.
--
Ben Reser <be...@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Multiple APR versions are a problem?
Posted by John Peacock <jp...@rowman.com>.
Ben Reser wrote:
>>You are using BDB 4.1.?? I think using 4.2.?? is more stable.
>
>
> There are problems with 4.2 in some certain circumstances. I simply
> don't think these circumstances warrant replacing the system bdb4.
There are known bad problems with 4.1 on multiple platforms under repeatable
circumstances with Subversion. This is the first I have heard of _any_ problem
with 4.2. In addition, there is no reason to replace the system bdb4 in order
to use 4.2. Could you document what problems led you to this somewhat suprising
change in accepted policy?
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Multiple APR versions are a problem?
Posted by Ben Reser <be...@reser.org>.
On Sat, Apr 03, 2004 at 01:11:11PM +0100, Barry Scott wrote:
> I'm using your packages and the problem is that you only build a subset
> of the apache modules that we are using. Now if I could use svnserver
> and avoid messing with apache that would be fine. But because of APR
> I cannot install svn at all and leave httpd2 as installed and working
> from the 9.2 distro.
Which ones do you need built? You're using 9.2 i586 right? Won't take
me long to build more apache modules.
> You are using BDB 4.1.?? I think using 4.2.?? is more stable.
There are problems with 4.2 in some certain circumstances. I simply
don't think these circumstances warrant replacing the system bdb4.
> So static link and avoid the reinstall-the-world problem! Or set a different
> so version so that more then one libapr.so can be installed. What do you
> think?
I really don't like static stuff. It's a pain to deal with security
wise. If I build a truly static I'm shipping a copies of numerous
libraries. All of which I have to monitor and rebuild and release if
they have a security issue. So I'm not inclined to put up static
versions of anything.
As far as changing libapr's so version. I won't do that. I think it's
inappropriate for me to do that. If I change the so version then in the
future my version may be incompatable with their version of the same
number. That's just wrong IMHO and totally messes up the point of
having the version numbers.
Besides, the APR lib I'm shipping should work fine with the Apache that
Mandrake is shipping. It might take some effort with rpm to get it
installed. But I believe that APR's compatability gurantees will keep
it working.
--
Ben Reser <be...@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Multiple APR versions are a problem?
Posted by Barry Scott <ba...@barrys-emacs.org>.
At 02-04-2004 09:41, Ben Reser wrote:
> > Its not possible to install the svn client without
> > replacing the httpd because of sharing libapr.
>
>Using my packages can solve this for you. I have all the dependencies
>solved for you. You can find my packages here:
>http://mirror.brain.org/linux/breser/mandrake/
I'm using your packages and the problem is that you only build a subset
of the apache modules that we are using. Now if I could use svnserver
and avoid messing with apache that would be fine. But because of APR
I cannot install svn at all and leave httpd2 as installed and working
from the 9.2 distro.
> > In our case we don't want to replace the httpd, so
> > it limits svn deployment.
>
>Why? If you're worried about support, I can assure you that my Apache
>packages will be kept up to date with security fixes. One of the
>machines that serves stuff for the Mandrake security team is running
>those packages.
You don't have all the modules we need built and I don't have the time
to do the builds myself.
>If you find bugs in my packages, I want to know about it. I'll be happy
>to fix them, I'm running them on the platforms I have up (including
>Mandrake 9.2).
You are using BDB 4.1.?? I think using 4.2.?? is more stable.
>APR isn't at 1.0 yet. As a result they're still finding and fixing
>problems...
So static link and avoid the reinstall-the-world problem! Or set a different
so version so that more then one libapr.so can be installed. What do you think?
Barry
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org