Michael and I researched and discussed this in IRC recently.
First of all, the code in the ecryptfs-utils pre-removal script is doing exactly what it is supposed to do -- it detects that you are in fact using ecryptfs for your encrypted home or encrypted private and the pre-removal script *refuses* to allow ecryptfs to be removed. Otherwise, if ecryptfs-utils was successfully removed, you would be completely locked out of your home or private, until you forcibly reinstalled ecryptfs-utils.
That said, there is a bug here, in why apt thinks that ecryptfs-utils can be removed.
Michael suggested that perhaps the best solution to this problem would be to have adduser recommend (rather than suggest) ecryptfs-utils. I agree with his assessment. I'm moving this bug over to adduser, and will fix it there in Natty.
This is, perhaps, a candidate for an SRU, IMHO, as there have been many, many duplicates.
Michael and I researched and discussed this in IRC recently.
First of all, the code in the ecryptfs-utils pre-removal script is doing exactly what it is supposed to do -- it detects that you are in fact using ecryptfs for your encrypted home or encrypted private and the pre-removal script *refuses* to allow ecryptfs to be removed. Otherwise, if ecryptfs-utils was successfully removed, you would be completely locked out of your home or private, until you forcibly reinstalled ecryptfs-utils.
That said, there is a bug here, in why apt thinks that ecryptfs-utils can be removed.
Michael suggested that perhaps the best solution to this problem would be to have adduser recommend (rather than suggest) ecryptfs-utils. I agree with his assessment. I'm moving this bug over to adduser, and will fix it there in Natty.
This is, perhaps, a candidate for an SRU, IMHO, as there have been many, many duplicates.