I can confirm this.
There were no problems with the first feisty-kernels. Yesterday I updated for the first time since about a month and then I received this error.
Chrooting into feisty from my edgy-install works, though.
I can confirm this.
There were no problems with the first feisty-kernels. Yesterday I updated for the first time since about a month and then I received this error.
Chrooting into feisty from my edgy-install works, though.