bzr-svn on Solaris 10

[Harald Meland]

[Russel Winder]

> On Mon, 2008-11-24 at 11:09 +0100, Harald Meland wrote:
>> [Russel Winder]
>> > |> ll /usr/lib/libresolv* /lib/libresolv*
>> 
>> Are those the same libresolv.so.2 paths that you get from
>> 
>>   ldd /home/users/russel/.bazaar/plugins_SunOS_sparc/svn/*.so | grep libresolv
>> 
>> ?
>
> |> ldd /home/users/russel/.bazaar/plugins_SunOS_sparc/svn/*.so | grep
> libresolv
>         libresolv.so.2 =>        /usr/lib/libresolv.so.2
>         libresolv.so.2 (SUNW_2.2.2) =>   (version not found)
>         libresolv.so.2 =>        /usr/lib/libresolv.so.2
>         libresolv.so.2 (SUNW_2.2.2) =>   (version not found)
>         libresolv.so.2 =>        /usr/lib/libresolv.so.2
>         libresolv.so.2 (SUNW_2.2.2) =>   (version not found)
>         libresolv.so.2 =>        /usr/lib/libresolv.so.2
>         libresolv.so.2 (SUNW_2.2.2) =>   (version not found)
> |> 
>
> It seems not. :-(

If you run the same command, but without the grep, you can see which
of the svn plugin's .so files are having troubles resolving
libresolv.so.2.  Could it be that you have some old ones still lying
around?

> I am guessing the SUNW_2.2.2 is the problem here. I guess I am going
> to have to back out all the Neon/Subversion upgrades.

Yeah, I'd guess that one of the libraries the svn plugin links against
have in turn been linked again version SUNW_2.2.2 of the resolver
library; unless you've upgraded the resolver library recently, your
recent Neon/Subversion update seems a likely culprit.

You could run ldd on binaries/libraries from those updated packages to
verify which one(s) are giving you trouble, and see if there are
further upgrades available to fix that.
-- 
Harald