On Jul 25, 2008, at 11:33 AM, François Giron wrote: <snip>
>>> >>> I run 'fink cleanup all', 'fink remove fink-buildlock- >>> gnumeric-1.8.1-3', but the result is the same. >>> >>> Suppression de fink-buildlock-gnumeric-1.8.1-3 ... >>> There is currently an active buildlock for the package >>> gnumeric (1.8.1-3) >>> meaning some other fink process is currently building it. >>> /sw/bin/dpkg : erreur de traitement de fink-buildlock- >>> gnumeric-1.8.1-3 (--remove) : >>> le sous-processus pre-removal script a retourné une erreur de >>> sortie d'état 1 >>> Des erreurs ont été rencontrées pendant >>> l'exécution : >>> fink-buildlock-gnumeric-1.8.1-3 >>> ### execution of /sw/bin/dpkg-lockwait failed, exit code 1 >>> ERROR: Can't remove package(s). If the above error message >>> mentions dependency >>> problems, you can try >>> fink remove --recursive fink-buildlock-gnumeric-1.8.1-3 >>> This will attempt to remove the package(s) specified as well as >>> ALL packages >>> that depend on it. >>> Failed: can't remove package fink-buildlock-gnumeric-1.8.1-3 >>> >>> % fink list -t fink-buildlock >>> Information about 7204 packages read in 5 seconds. >>> p fink-buildlock [virtual package] >>> *i* fink-buildlock-gnumeric-1.8.1-3 2008.07.25-10.07.04 >>> Package compile-time lockfile >>> >> >> if you're sure that you don't have a window open that has a build >> of gnumeric in it (possibly suspended), then the best things I can >> think of trying are to use "ps ax" to see if you still have a >> process around that became disconnected and then to "kill" it if >> there is one; or just to reboot to make sure any such process is >> dead. This will probably require a bit of additional work to clean >> up, but let's start just by getting rid of the build lock. > > Ok. The problem seems to be these: during update-all (278 packages!) > the gnumeric update failed and Terminal.app had a locking. I quit > and open my session and remove gnumeric to continue the update-all > with Eterm. But I see with the 'ps ax' this: > > 1258 ?? E 0:00.00 (Terminal) > > I reboot, and all is OK. > Thanks You're welcome. The build locks work reasonably well, but in cases where a terminal crashes, they may not get deactivated properly, as you have experienced. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
