[Touch-packages] [Bug 1605160] Re: kernel autoremove not working

2016-11-03 Thread Julian Andres Klode
*** This bug is a duplicate of bug 1472351 *** https://bugs.launchpad.net/bugs/1472351 ** This bug has been marked a duplicate of bug 1472351 autoremove keeps *all* providers of virtual rdeps unconditionally -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1605160] Re: kernel autoremove not working

2016-10-31 Thread Alberto Salvia Novella
** Changed in: apt (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1605160 Title: kernel autoremove not working Status in apt

[Touch-packages] [Bug 1605160] Re: kernel autoremove not working

2016-10-24 Thread thermoman
bug #1472351 seems to be the cause for this issue. I guess you have some ZFS package installed that has a Recommends tag for linux-headers or linux-image, too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu.

[Touch-packages] [Bug 1605160] Re: kernel autoremove not working

2016-10-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu.

[Touch-packages] [Bug 1605160] Re: kernel autoremove not working

2016-10-24 Thread thermoman
I see > NonfreeKernelModules: zfs zunicode zcommon znvpair zavl in your report. It might have something to do with packages that install extra kernel modules ultimately preventing autoremoval of the old kernel images. ZFS in your case, virtualbox in my case. -- You received this bug

[Touch-packages] [Bug 1605160] Re: kernel autoremove not working

2016-10-24 Thread thermoman
Do you have by any chance virtualbox installed? Please see my bug #1636203 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1605160 Title: kernel autoremove not working Status

[Touch-packages] [Bug 1605160] Re: kernel autoremove not working

2016-07-21 Thread David Kalnischkies
So apt would autoremove them if it could, like it already did with the linux-image-extra packages – so I guess as before: kernel module package depending on the images perhaps via indirection (provides), probably on of the "NonfreeKernelModules: zfs zunicode zcommon znvpair zavl" (or another, I am

[Touch-packages] [Bug 1605160] Re: kernel autoremove not working

2016-07-21 Thread Hadmut Danisch
Definitely no manual interaction, fresh install recently. # apt-mark showauto ^linux-image-.* linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic linux-image-4.4.0-28-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-28-generic

[Touch-packages] [Bug 1605160] Re: kernel autoremove not working

2016-07-21 Thread David Kalnischkies
Are you sure you haven't marked these kernels as manually installed somehow? Perhaps there is also something depending on them still like some installed out-of-tree kernel modules. The output of the following three commands can be helpful to figure out if apt would consider autoremoving them if