Actions
Bug #1155
openIf ldv-manager is stopped in kernel unpacking it doesn't work then
Start date:
04/30/2011
Due date:
% Done:
0%
Estimated time:
Detected in build:
svn
Platform:
Published in build:
Description
So if you invoke ldv-manager for the first time in a given directory and send Cntl+C during kernel preparing, then you cannot make it to work without auxiliary files erasing made by hand:
( flock 200; export LDV_ENVS_TARGET=/home/joker/work/14_driver/32_1a/inst/current ; echo "Preparing kernel linux-2.6.31.6 from linux-2.6.31.6.tar.bz2..." ; ldv kmanager --action=add --src=/home/joker/work/14_driver/32_1a/linux-2.6.31.6.tar.bz2 --extractor=linux-vanilla --name=linux-2.6.31.6 >/dev/null ) 200>.lock Preparing kernel linux-2.6.31.6 from linux-2.6.31.6.tar.bz2... make: *** [tags/current/env.linux-2.6.31.6] Error 1
Updated by Evgeny Novikov over 13 years ago
I suggest that this is due to an installation flag is created before an installation is performed (for the first invocation):
touch tags/current/installed ( flock 200; export LDV_ENVS_TARGET=/home/joker/work/14_driver/32_1a/inst/current ; echo "Preparing kernel linux-2.6.31.6 from linux-2.6.31.6.tar.bz2..." ; ldv kmanager --action=add --src=/home/joker/work/14_driver/32_1a/linux-2.6.31.6.tar.bz2 --extractor=linux-vanilla --name=linux-2.6.31.6 >/dev/null ) 200>.lock Preparing kernel linux-2.6.31.6 from linux-2.6.31.6.tar.bz2... tar: Record size = 8 blocks
Actions