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

RE: upgrade to 1.2.0 not working

From: Richard Andrews <randrews_at_transzap.com>
Date: 2005-07-01 17:42:04 CEST

Ok I think that we are making progress but we still have one major
issue. When a developer does a commit the process just hangs and never
completes.

As far as what we have done to get this far we looked at the rpm that we
were using and sure enough there were no ls_base libraries included in
it. We switched to a different rpm that did have the ls_base libraries
and the database would not recognize the db4-4.2 database. Our system
has both db4-4.1 and db4-4.2 on it and the sysadmin who originally
installed svn (and is no longer with the company) had some how
configured it to use the 4.2.

So we had a test system with rhel4 on it which comes with db4.2. We
Installed a svn rpm for rhel4 on it. It saw the repository and we were
able to do a dump. I then created a new repository on the development
system using fsfs filesystem type and loaded the dump into the new
repository. It all worked fine except when I created the new repository
the process locked up and never returned to a $ prompt. I had to kill
the process from a root session. However svnadmin saw it and the load
went with no errors. But now like I said above when you do a commit it
just hangs.

Any help is much appreciated.

Rich A.

> -----Original Message-----
> From: kfogel@newton.ch.collab.net [mailto:kfogel@newton.ch.collab.net]
On
> Behalf Of kfogel@collab.net
> Sent: Thursday, June 30, 2005 1:19 PM
> To: Richard Andrews
> Cc: users@subversion.tigris.org
> Subject: Re: upgrade to 1.2.0 not working
>
> "Richard Andrews" <randrews@transzap.com> writes:
> > We did not build the rpm we downloaded it from the binary download
site
> > http://summersoft.fay.ar.us/pub/subversion/latest
> >
> > The rhel-3/bin directory. Do you think that this rpm was not built
> > correctly?
>
> I don't know -- but I would suggest contacting the builder of the RPM
> (I presume a bug address is listed?)
>
> Do you have Berkeley DB installed anywhere on your system? Did maybe
> someone *uninistall* BDB after installing Subversion? That might
> result in this error, now that I think about it.
>
> -Karl
>
> > > -----Original Message-----
> > > From: kfogel@newton.ch.collab.net
[mailto:kfogel@newton.ch.collab.net]
> > On
> > > Behalf Of kfogel@collab.net
> > > Sent: Thursday, June 30, 2005 8:19 AM
> > > To: Richard Andrews
> > > Cc: users@subversion.tigris.org
> > > Subject: Re: upgrade to 1.2.0 not working
> > >
> > > "Richard Andrews" <randrews@transzap.com> writes:
> > > > I am brand new to SVN and need some help. I upgraded our
companies
> > svn
> > > > 1.0 to the current 1.2.0 so we could create a new repository
using
> > fsfs.
> > > > After the upgrade the svn admin tools no longer work on our
original
> > > > repository. I get the following message.
> > > >
> > > > svnlook: Failed to load module for FS type 'bdb'
> > > >
> > > > svnadmin give me the same error also. I would appreciate any
help I
> > can
> > > > get.
> > >
> > > It sounds like when you built 1.2, you didn't configure with
> > > BerkeleyDB (or anyway, configure didn't find BDB). Try
rebuilding,
> > > and look carefully at your configuration output to see what it
says
> > > about Berkeley.
> > >
> > > -Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 1 17:57:20 2005

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