Christian Perrier wrote: > Quoting Joey Hess (joeyh@debian.org): > > > I can reproduce this in vmware. It is not just vmware being slow either. > > set -x shows it is in decode_recipe. It gets the ram size, and then > > apparently $1 is not set, so the cat without an argument hangs. > > decode_recipe is being called without a recipe name to decode. > > partman-auto/choose_recipe is somehow set to "". I did not go back > > further. > > > > Either this is somehow triggered by the vmware environment, or it is > > fixed in version 7 of partman-auto. Version 7 will be in tonight's CD > > images, so we can see then. > > The problem is still there with the night's CD. The only difference is > the progress bar showing 90% and no more 88%...:-)) > > In VmWare, of course... Ok, I've found that this is just that we have small drives and partman-auto is not able to come up with any recipes that fit (which is why it doesn't prompt for any), and it lacks a check for this. I'll add a check. My vmware drive is 300 mb. Memory is 95 mb. Yours? -- see shy jo
Attachment:
signature.asc
Description: Digital signature