On 3 May 2013 20:24, Steve J. <email address hidden> wrote:
> On Fri, May 03, 2013 at 01:09:09AM -0000, Daniel Hartwig wrote:
>> > This is a problem, because it renders the fix in this bug,
>> > https://bugs.launchpad.net/ubuntu/+source/apt/+bug/923876 (Limit and
>> > clean-up kernel images and headers automatically in LTS) ineffective,
>> > since apt-get autoremove will not remove packages which are marked as
>> > manually installed.
>> >
>>
>> When the kernel image is upgraded again, 3.2.0-41 will be marked auto.
>> The kernel cleanup hack works by putting the active kernel image
>> outside of APTs autoremove system, i.e. to mark it manually installed.
>
> I see, but that's not the behavior that I'm seeing (the host I picked to
> use as an example wasn't a very good one, sorry). I'm seeing all the
> kernel packages remaining marked manual, and they're never being marked
> as auto after new updates.
>
Yes that is my mistake, the cleanup does not change the marking at
all. If they are currently manual you will have to mark them
auto-installed to have the cleanup work. If upgrading
'linux-image-generic' leaves you with a linux-image that is marked
manual, that is of course a problem.
How do you upgrade the systems, in your original message you mention
aptitude and unattended-upgrades?
That issue does not apply here as the kernel upgrades you identified
usually come as new packages. It would apply if e.g. after an upgrade
you found that 'linux-image-generic' had changed from auto-installed
to manual.
On 3 May 2013 20:24, Steve J. <email address hidden> wrote: /bugs.launchpad .net/ubuntu/ +source/ apt/+bug/ 923876 (Limit and
> On Fri, May 03, 2013 at 01:09:09AM -0000, Daniel Hartwig wrote:
>> > This is a problem, because it renders the fix in this bug,
>> > https:/
>> > clean-up kernel images and headers automatically in LTS) ineffective,
>> > since apt-get autoremove will not remove packages which are marked as
>> > manually installed.
>> >
>>
>> When the kernel image is upgraded again, 3.2.0-41 will be marked auto.
>> The kernel cleanup hack works by putting the active kernel image
>> outside of APTs autoremove system, i.e. to mark it manually installed.
>
> I see, but that's not the behavior that I'm seeing (the host I picked to
> use as an example wasn't a very good one, sorry). I'm seeing all the
> kernel packages remaining marked manual, and they're never being marked
> as auto after new updates.
>
Yes that is my mistake, the cleanup does not change the marking at image-generic' leaves you with a linux-image that is marked
all. If they are currently manual you will have to mark them
auto-installed to have the cleanup work. If upgrading
'linux-
manual, that is of course a problem.
How do you upgrade the systems, in your original message you mention upgrades?
aptitude and unattended-
> This bug looks similar to /bugs.launchpad .net/aptdaemon/ +bug/1078544, however, I'm running
> https:/
> a version of aptdaemon that supposedly has this fix applied.
That issue does not apply here as the kernel upgrades you identified image-generic' had changed from auto-installed
usually come as new packages. It would apply if e.g. after an upgrade
you found that 'linux-
to manual.