On Jan 8, 2010, at 10:05 AM, Alexander Hansen wrote:

> On 1/8/2010 2:58 AM, monipol wrote:
>> On 08/01/2010, at 04:28, John Garvin wrote:
>> 
>>> When I say 'fink update-all' svn-shlibs is having trouble  
>>> installing. It
>>> seems to be a problem finding the Berkeley DB, even though it seems  
>>> to be
>>> installed. I've attached the result of 'fink update-all' and the  
>>> result of
>>> 'list db4'.
>>> 
>> From the attached file:
>> 
>> configure: WARNING: APR-UTIL may or may not be using the specified
>>                      Berkeley DB at `/sw/include/db4:/sw/lib'.  Using  
>> the       Berkeley DB
>>                      supplied by APR-UTIL.
>> checking for availability of Berkeley DB... no
>> configure: error: Berkeley DB 4.1.25 wasn't found.
>> ### execution of /var/tmp/tmp.1.TPU9xO failed, exit code 1
>> Removing runtime build-lock...
>> Removing build-lock package...
>> /sw/bin/dpkg-lockwait -r fink-buildlock-svn-1.4.6-14
>> (Reading database ... 145517 files and directories currently installed.)
>> Removing fink-buildlock-svn-1.4.6-14 ...
>> Failed: phase compiling: svn-1.4.6-14 failed
>> 
>> I've noticed other users have reported this already but we haven't  
>> heard from the maintainer (CC'ed). That said, do you really need to  
>> use this old version? Try running
>> 
>> fink remove svn-shlibs
>> 
>> If Fink is able to remove svn-shlibs then no other package requires  
>> it. The latest Subversion package is called svn, version 1.6.6, with  
>> corresponding svn15-shlibs for its shared libraries.
>> 
>> 
>> Cheers,
>> 
>> --
>> monipol
>> http://finkers.wordpress.com
>> 
>> Submitting a Fink bug report? Read this:
>> http://www.finkproject.org/doc/netiquette/index.php
>> http://finkers.wordpress.com/2009/06/03/bug-reports/
>> 
>> 
>> 
> (please don't attach text files in the future, since people are going to
> have to paste back from them for context when they reply--inline text is
> much better)
> 
> This probably is coming in via a dependency from some other package, and
> once we can get a handle on which one it is via a removal attempt,
> _that_ maintainer can be contacted and we can see if the package can be
> convinced to use a modern svn.
> 
> For now, hold off on using update-all.

I've now hacked svn-1.4.6 to build. I have no idea if it actually works. I've 
marked it as obsolete and any packages using it should change to svn15.

Daniel

Attachment: smime.p7s
Description: S/MIME cryptographic signature

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to