The relevant error is
---
Setting up linux-image-2.6.31-20-generic (2.6.31-20.58) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.31-20-generic
Failed to symbolic-link boot/initrd.img-2.6.31-20-generic to initrd.img: File exists
dpkg: error processing linux-image-2.6.31-20-generic (--configure):
subprocess installed post-installation script returned error exit status 17
It is probably because you used the same name for your custom kernel than the official one. When you create a custom kernel it is recommended to use a custom extension to avoid conflicts between packages.
I'm closing this report because it is not a bug with Ubuntu. Don't hesitate to reopen if you're still experiencing this issue after (re)moving your custom package.
Thanks for your report.
The relevant error is 2.6.31- 20-generic (2.6.31-20.58) ... img-2.6. 31-20-generic img-2.6. 31-20-generic to initrd.img: File exists 2.6.31- 20-generic (--configure):
---
Setting up linux-image-
Running depmod.
update-initramfs: Generating /boot/initrd.
Failed to symbolic-link boot/initrd.
dpkg: error processing linux-image-
subprocess installed post-installation script returned error exit status 17
It is probably because you used the same name for your custom kernel than the official one. When you create a custom kernel it is recommended to use a custom extension to avoid conflicts between packages.
I'm closing this report because it is not a bug with Ubuntu. Don't hesitate to reopen if you're still experiencing this issue after (re)moving your custom package.
Thanks.