As told before, the issue seems to be fixed even in apt 1.6.14, but I tested the proposed 1.6.17 anyway. Autoremove did not (try to) remove current kernel even with that one, but it removes one more kernel than the old one (which is desired by developers, I assume).
As told before, the issue seems to be fixed even in apt 1.6.14, but I tested the proposed 1.6.17 anyway. Autoremove did not (try to) remove current kernel even with that one, but it removes one more kernel than the old one (which is desired by developers, I assume).