Comment 1 for bug 1519049

Revision history for this message
Zoltan Balogh (bzoltan) wrote :

Thanks for reporting this issue. The real problem is that terminating a chroot bootsrapping is really a very dirty thing. It can leave a half creted schroot on your system what can be removed manually. Careless removal of broken chroots can cause serious problems.

I know for example an very stupid user who tried to just sudo rm the broken choot... while the $HOME was mounted. That very stupid user was me :)

I know it is annoying, we are thinking about alternative solutions and investigating the topic, but I doubt it will be resolved soon. We can remove the "question" from that dialog and simple state that sorry this is an operation what can not be cancelled.

The one good alternative of boostraping the chroot Kit is to to use static Kits. That comes from the ubuntu-sdk-api-15.04-[armhf|i386] packages. sudo apt-get install will pull them from the SDK PPA.