entry point error from bzr-svn if incompatible SVN client is installed

Bug #386079 reported by Wally Lawless
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Wishlist
Unassigned
subvertpy
Invalid
Undecided
Unassigned

Bug Description

When other svn dll's are installed on a windows machine, bzr-svn may fail to load the svn dll's:
...
The procedure entry point svn_txdelta_run could not be located in the dynamic link library libsvn_delta-1.dll
...

Vincent Ladeuil (vila)
affects: bzr → bzr-svn
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

this is a problem in the bzr setup build of subvertpy.

affects: bzr-svn → bzr
Revision history for this message
Wally Lawless (wally-power-coder) wrote :

Do you happen to know if there is a way to work around it? Or should I just wait for an updated build?

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

No idea, sorry (I'm not on Windows).

Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 386079] Re: bzr-svn throwing procedure entry point errors

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jelmer Vernooij wrote:
> No idea, sorry (I'm not on Windows).
>

My best guess is that he has a second copy of the libsvn dlls around,
and they are in PATH, and they are built against a different version of
APR. (Specifically, when you go to install, you can pick whether you
want 2.0 or 2.2, IIRC, the dlls seem to be named the same, but are not
compatible.)

It was a real pain when I was getting it to work, it is possible
something was tweaked and now it is broken again.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAko2WIwACgkQJdeBCYSNAAM3XACfRVt4lSI0TK804YEG2nwyNdKy
J3gAoKzSsV0amgQya/Eeyqq+IKAxfbN0
=csrb
-----END PGP SIGNATURE-----

Revision history for this message
Wally Lawless (wally-power-coder) wrote : Re: bzr-svn throwing procedure entry point errors

Well, it looks like I've made some progress based on the previous comment by John. Looking through my PATH variables I did see a c:\Program Files\Subversion entry in there ahead of the bazaar entry. This folder contained many dlls with the same names as the ones bazaar is looking for. I renamed the folder on the filesystem to be Subversion_old and now when I run an bzr update or commit I don't get the procedure entry point errors popping up and the update appears to succeed. However, for the commit, I get an error stating 'ERROR: Unable to look up default port for svn' which I believe may be a separate issue.

Should I submit a new bug report for the port issue?

Thanks,
Wally

Revision history for this message
John A Meinel (jameinel) wrote :

The 'port' bug is bug #386079, which should be fixed in the next release.

Revision history for this message
Robert Collins (lifeless) wrote :

Critical as its a broken installer.

Changed in bzr:
importance: Undecided → Critical
status: New → Confirmed
Revision history for this message
John A Meinel (jameinel) wrote :

I'm not sure what you are considering Robert. How can we fix it finding dlls that are already present on the machine?

The 'port' issue is already fixed and will be in 1.16, and is a different bug anyway.

The installer installs dlls into its own directory which work correctly. If you are going to mark it as 'release blocking' it would be good to have an answer to what you think we should do.

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 386079] Re: bzr-svn throwing procedure entry point errors

On Tue, 2009-06-16 at 15:09 +0000, John A Meinel wrote:
> I'm not sure what you are considering Robert. How can we fix it finding
> dlls that are already present on the machine?
>
> The 'port' issue is already fixed and will be in 1.16, and is a
> different bug anyway.
>
> The installer installs dlls into its own directory which work correctly.
> If you are going to mark it as 'release blocking' it would be good to
> have an answer to what you think we should do.

Well, I have marked it as something we should be examining asap. As per
the recent mailing list thread release blocking would be to set a
milestone too.

Anyhow in this case I would say shipping the right dll in the installer
would fix it wouldn't it? or perhaps this isn't a bzr bug at all and we
should say either 'invalid' or file a wishlist that we should catch the
exception and provide a better error, and make this bug and the
backtrace into a FAQ for windows users.

-Rob

Revision history for this message
Robert Collins (lifeless) wrote :

So I think we probably want to make a FAQ about this so people can solve it. We should also see if we can change the installer to either detect, or setup bzr without the SVN client in its path, so the wrong dll's can't be found.

description: updated
summary: - bzr-svn throwing procedure entry point errors
+ entry point error from bzr-svn if incompatible SVN client is installed
Changed in bzr:
importance: Critical → Wishlist
Jelmer Vernooij (jelmer)
Changed in subvertpy:
status: New → Invalid
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers