cron.daily/apt reports MarkUpgrade() called on a non-upgrable pkg: 'linux-headers..."

Bug #1527166 reported by latimerio
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
python-apt (Ubuntu)
Triaged
Low
Unassigned
update-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Today I received the following messages from /etc/cron.daily/apt on my 14.04 LTS server

MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-3.13.0-73'
MarkUpgrade() called on a non-upgrable pkg: 'linux-image-extra-3.13.0-73-generic'
MarkUpgrade() called on a non-upgrable pkg: 'linux-image-3.13.0-73-generic'
MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-3.13.0-73-generic'

First of all I suppose the message should read non-upgradable
non-upgrable is possibly incorrect and should be corrected.

Secondly I have no clue, what this message means so the error message should be revised to give more details.

I think this as a minor bug but messages should always be correct, precise and possibly helpful.

Tags: trusty

Related branches

latimerio (fomember)
description: updated
tags: added: trusty
Revision history for this message
Brian Murray (brian-murray) wrote :

The message and typo comes from python-apt.

Changed in python-apt (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

Seen in an email this morning from a 16.04 system:
/etc/cron.daily/apt:
MarkUpgrade() called on a non-upgrable pkg: 'linux-image-4.4.0-59-generic'
MarkUpgrade() called on a non-upgrable pkg: 'linux-tools-3.13.0-107-generic'
MarkUpgrade() called on a non-upgrable pkg: 'linux-tools-3.13.0-107'
MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-4.4.0-59-generic'
MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-4.4.0-59'
MarkUpgrade() called on a non-upgrable pkg: 'linux-cloud-tools-3.13.0-107'
MarkUpgrade() called on a non-upgrable pkg: 'linux-cloud-tools-3.13.0-107-generic'

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in update-manager (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.