explanation:
- There is a file in the place of a directory preventing file copy and thus failure of post-installation script
(for those here looking for a solution)
workaround:
- go to "/lib/modules" where there should be a bunch of directories named for kernel versions (like "2.6.22-14-386")
- check for a kernel version which has a file rather in the place of a directory
- ("ls -lrt" shows "-rw-r--r-- 1 root root 0 2008-06-04 06:21 2.6.22-14-386")
- remove that file
- (sudo rm 2.6.24-21-386)
- make a directory in its place (I skipped this step)
- (sudo mkdir 2.6.24-21-386)
- run "sudo dpkg --configure -a"
- problem solved.
It should be noted that you should NOT try to reboot before fixing this as you may not be able to boot your machine with a half-configured upgrade.
I would mark as duplicate, but didn't want to make any assumptions.
The bug https:/ /bugs.launchpad .net/ubuntu/ +source/ module- init-tools/ +bug/366694 appears to be the same, and the report contains an explanation and work around which worked for me:
explanation:
- There is a file in the place of a directory preventing file copy and thus failure of post-installation script
(for those here looking for a solution)
workaround:
- go to "/lib/modules" where there should be a bunch of directories named for kernel versions (like "2.6.22-14-386")
- check for a kernel version which has a file rather in the place of a directory
- ("ls -lrt" shows "-rw-r--r-- 1 root root 0 2008-06-04 06:21 2.6.22-14-386")
- remove that file
- (sudo rm 2.6.24-21-386)
- make a directory in its place (I skipped this step)
- (sudo mkdir 2.6.24-21-386)
- run "sudo dpkg --configure -a"
- problem solved.
It should be noted that you should NOT try to reboot before fixing this as you may not be able to boot your machine with a half-configured upgrade.
I would mark as duplicate, but didn't want to make any assumptions.