On Tue, Apr 8, 2014 at 1:32 PM, Alexander Hansen
<alexanderk.han...@gmail.com> wrote:
> On 4/8/14, 10:20 AM, Bill Waggoner wrote:
>>
>> I'm trying to install rvm and it calls fink to install a few things:
>>
>> fink --yes install automake1.13 gcc48 libyaml libyaml-shlibs libksba8
>> libksba8-shlibs sqlite3
>>
>>
>> Unfortunately it captures any output so I didn't see what was
>> happening. I waited over an hour and nothing was happening (it did
>> prompt for my password so I know fink got started at least ...) so I
>> killed it.
>>
>>
>> Maybe that wasn't smart but it is what it is.
>>
>> So I tried installing the packages manually and get this:
>>
>> ---
>>
>> `--> fink install automake1.13 gcc48 libyaml libyaml-shlibs libksba8
>> libksba8-shlibs sqlite3
>> Information about 8731 packages read in 0 seconds.
>> The following package will be installed or updated:
>> gcc48
>> The following 2 additional packages will be installed:
>> gcc48-compiler gcc48-shlibs
>> Do you want to continue? [Y/n]
>> Setting runtime build-lock...
>> dpkg-deb -b /sw/src/fink.build/root-fink-buildlock-gcc48-4.8.2-1001
>> /sw/src/fink.build
>> dpkg-deb: building package `fink-buildlock-gcc48-4.8.2-1001' in
>>
>> `/sw/src/fink.build/fink-buildlock-gcc48-4.8.2-1001_2014.04.08-13.13.40_darwin-x86_64.deb'.
>> Installing build-lock package...
>> /sw/bin/dpkg-lockwait -i
>>
>> /sw/src/fink.build/fink-buildlock-gcc48-4.8.2-1001_2014.04.08-13.13.40_darwin-x86_64.deb
>> Waiting up to 300 seconds for access to the dpkg database...
>> Timed out, cancelling operation!
>> ### execution of /sw/bin/dpkg-lockwait failed, exit code 1
>> Failed: buildlock failure
>>
>> Timed out, cancelling operation!
>> ### execution of /sw/bin/dpkg-lockwait failed, exit code 1
>> Can't set build lock for gcc48 (4.8.2-1001)
>>
>> If any of the above dpkg error messages mention conflicting packages
>> or missing dependencies -- for example, telling you that the
>> package fink-buildlock-gcc48-4.8.2-1001 conflicts with something else
>> -- fink has probably gotten confused by trying to build
>> many packages at once. Try building just this current package gcc48
>> (i.e, "fink build gcc48"). When that has completed
>> successfully, you could retry whatever you did that led to the present
>> error.
>>
>> Regardless of the cause of the lock failure, don't worry: you have not
>> wasted compiling time! Packages that had been completely
>> built before this error occurred will not have to be recompiled.
>>
>> See https://github.com/fink/fink/wiki/Buildlocks for more information.
>> /sw/bin/dpkg-lockwait -r fink-buildlock-gcc48-4.8.2-1001 >/dev/null
>> Waiting up to 300 seconds for access to the dpkg database...
>>
>> ---
>>
>> And there it sits ...
>>
>> Any suggestions?
>>
>> Bill W
>>
>
> Check "ps" for another dpkg process. "dpkg-lockwait" deliberately prevents
> multiple dpkg operations to reduce the chance of corrupting the dpkg
> database. Otherwise, it's possible that you've got an orphaned lock file in
> /sw/var/lib/dpkg/lock
>
> --
> Alexander Hansen, Ph.D.
> Fink User Liaison
> My package updates: http://finkakh.wordpress.com/
Ah. Yes, I see this:
`--> ps -ef|grep dpkg
0 49990 61739 0 1:03PM ttys000 0:00.03 dpkg -r
fink-buildlock-gcc48-4.8.2-1001
0 49991 49990 0 1:03PM ttys000 0:00.14 /usr/bin/perl -w
/sw/bin/fink-virtual-pkgs --dpkg
Now what?
Bill W
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users
