Because the linux-generic fix in question was an ABI change, a new package not previously installed was pulled. However, it was not from security either:
$ apt-cache policy linux-image-generic linux-image-generic: Installed: 2.6.32.25.27 Candidate: 2.6.32.25.27 Version table: *** 2.6.32.25.27 0 500 http://fi.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 2.6.32.24.25 0 500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages 2.6.32.21.22 0 500 http://fi.archive.ubuntu.com/ubuntu/ lucid/main Packages $ apt-cache policy linux-image-2.6.32-25-generic linux-image-2.6.32-25-generic: Installed: 2.6.32-25.44 Candidate: 2.6.32-25.44 Version table: *** 2.6.32-25.44 0 500 http://fi.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status $
(These commands executed after applying the update. Nothing vsible in kpackagekit at this point of time anymore of course)
Because the linux-generic fix in question was an ABI change, a new package not previously installed was pulled. However, it was not from security either:
$ apt-cache policy linux-image-generic generic: fi.archive. ubuntu. com/ubuntu/ lucid-updates/main Packages dpkg/status security. ubuntu. com/ubuntu/ lucid-security/main Packages fi.archive. ubuntu. com/ubuntu/ lucid/main Packages 2.6.32- 25-generic 2.6.32- 25-generic: fi.archive. ubuntu. com/ubuntu/ lucid-updates/main Packages dpkg/status
linux-image-
Installed: 2.6.32.25.27
Candidate: 2.6.32.25.27
Version table:
*** 2.6.32.25.27 0
500 http://
100 /var/lib/
2.6.32.24.25 0
500 http://
2.6.32.21.22 0
500 http://
$ apt-cache policy linux-image-
linux-image-
Installed: 2.6.32-25.44
Candidate: 2.6.32-25.44
Version table:
*** 2.6.32-25.44 0
500 http://
100 /var/lib/
$
(These commands executed after applying the update. Nothing vsible in kpackagekit at this point of time anymore of course)