linux-libc-dev update dependency problem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: update-manager
On 6.10 i386. linux-libc-dev is permanently being reported an available update from 2.6.17.1-11.37 to 2.6.20-15.27, although the system is using kernels no later than 2.6.17-11 (all kernels from standard update process - no 'extra' kernels installed by hand). It seems that the libc kernel header package is not checking the installed kernel versions. This may in part be related to bug #37937, in which the fact that the linux-libc-dev is treated as a separate package causes problems. The rejection of that bug seemed to miss the point, viz :-
On mar, 2006-04-04 at 01:24 +0000, Matt Zimmerman wrote:
> The headers are not installed by default; if you want them, install the corresponding linux-headers-<foo> package for the linux-<foo> package you are using, and it will track the same versions.
>
> ** Changed in: Ubuntu
> Status: Unconfirmed => Rejected
The headers are NOT tracking the versions of the kernel (if i'm reading Matt replies correctly). It makes no sense, and is a potential build issue, to update the headers regardless of the kernel version... also irritating that you cannot 'turn off' the update warning from the update-manager without uninstalling the package.. but this is linked with the dependency issue between the kernel and the header package which seems to have been ignored. Shurly shome mysteak.
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.