The following package will be installed or updated:
gnome-terminal
dpkg-deb -b /sw/src/fink.build/root-fink-buildlock-gnome-terminal-2.6.1-8 /sw/src/fink.build
dpkg-deb: building package `fink-buildlock-gnome-terminal-2.6.1-8' in `/sw/src/fink.build/fink-buildlock-gnome-terminal-2.6.1-8_2005.06.06-14.33.00_darwin-powerpc.deb'.
Setting build lock...
dpkg -i /sw/src/fink.build/fink-buildlock-gnome-terminal-2.6.1-8_2005.06.06-14.33.00_darwin-powerpc.deb
(Reading database ... 70667 files and directories currently installed.)
Preparing to replace fink-buildlock-gnome-terminal-2.6.1-8 2005.06.02-21.49.48 (using .../fink-buildlock-gnome-terminal-2.6.1-8_2005.06.06-14.33.00_darwin-powerpc.deb) ...
Error: fink thinks that the package it is about to build:
gnome-terminal (2.6.1-8)
is currently being built by another fink process. That build
process has a timestamp of:
2005.06.02-21.49.48
If this is not true (perhaps the previous build process crashed?),
just remove the fink package:
fink remove fink-buildlock-gnome-terminal-2.6.1-8
Then retry whatever you did that led to the present error.
dpkg: warning - old pre-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
/sw/bin/dpkg: error processing /sw/src/fink.build/fink-buildlock-gnome-terminal-2.6.1-8_2005.06.06-14.33.00_darwin-powerpc.deb (--install):
subprocess new pre-removal script returned error exit status 1
Errors were encountered while processing:
/sw/src/fink.build/fink-buildlock-gnome-terminal-2.6.1-8_2005.06.06-14.33.00_darwin-powerpc.deb
### execution of dpkg failed, exit code 1
Can't set build lock for gnome-terminal (2.6.1-8)
If any of the above dpkg error messages mention conflicting packages --
for example, telling you that fink-buildlock-gnome-terminal-2.6.1-8
conflicts with something else -- fink has probably gotten confused by trying
to build many packages at once. Try building just this current package
gnome-terminal (i.e, "fink build gnome-terminal"). 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.
Failed: buildlock failure