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

Re: bad subversion-1.2.0-1.rhel3.i386.rpm

From: David Summers <david_at_summersoft.fay.ar.us>
Date: 2005-07-08 00:28:21 CEST

On Wed, 6 Jul 2005 kfogel@collab.net wrote:

> "Richard Andrews" <randrews@transzap.com> writes:
>> David and Developers at Subversion.tigris.org
>> I took a look at the rpm changelog and sure enough it is stated right at
>> the top that you are dropping support for the BDB backend on this rpm.
>> I am fairly new to Linux (have had considerable SCO and HPUX
>> experience in the past) and did not know to view this. I don't know if
>> this was a newbie mistake or not but it was confusing to me when the
>> Subversion 1.2.0 release notes goes out of its way to state that
>> support for BDB is not going away and then find out that it was
>> dropped on purpose in the creation of this rpm. I also realize that the
>> summersoft download site is not part of Tigris but you do list/link to
>> this site for rpm downloads.
>> I guess what I am trying to get at is if you think that this was just
>> a newbie mistake so be it, water under the bridge and all that.
>> However if there is a good chance that others might make the same
>> mistake that we made could there be some effort into putting up a more
>> overt warning for them and possibly save them the hours of
>> troubleshooting that we had to go through.
> You're right that the situation is bad -- very bad for people who have
> legacy BDB repositories and need to upgrade Subversion via RPM.
> I initially thought "How could we have let this happen?" Then I
> talked to Ben Collins-Sussman, who reminded me that David Summers (our
> RPM maintainer) posted a long time ago saying he was having trouble
> getting the RPMs to work with BDB, and asking for help. No one was
> able to help him, and he never found a way to get it working, so in
> frustration he finally decided to drop BDB support from the RPMs. I
> don't have the mail thread handy, but he warned us he was going to do
> that, and we had no better idea.
> So this isn't David's fault at all. We're just in a bad situation
> w.r.t. our RPMs now, and no one knows what to do. David, did you
> contact anyone at RedHat about these problems? Did (say) Joe Orton
> ever comment on it? I think he's pretty expert in RPM packaging, and
> goodness knows he's familiar with Subversion...

Note that this is ONLY with the Redhat Enterprise Linux 3 version. All
the other RPMs I package still have BDB capability.

Max Bowsher was interested in taking a look at it back a few weeks ago and
I gave him an account on my box but I have not heard from him yet. I
assume that he ran into the same problems I ran into and was not able to
solve it.

We could put a big red or yellow warning on the downloads page if you
think that would be appropriate.

Any ideas are welcome. I didn't like doing it but I liked less all the
PHP, APR, HTTPD, BDB mess that it caused and also users were always
complaining that they had problems installing it.

David Wayne Summers        "Linux: Because reboots are for hardware upgrades!"
david_at_summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  0B44 B118 85CC F4EC 7021  1ED4 1516 5B78 E320 2001
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 8 00:29:08 2005

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

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