[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#736763: bugs.debian.org: apache2 not removed after purging smokeping



Control: tags -1 + moreinfo

Hi Jason & Jean-Michel,

Jason, your bugreport got reassigned to apt today,
Jean-Michel, you reassigned it to us.

My question for both of you is how I can reproduce this problem as if I build a
minbase chroot of testing, install smokeping and after that call
$ apt-get autoremove --purge smokeping
it happily removes apache2 with smokeping (and javascript-common, too).

This keeps many packages installed (204 newly installed vs 78 removed), but
these are all recommends/suggests of other packages still installed.

Letting the autoremover run free with
-o APT::AutoRemove::RecommendsImportant=false -o APT::AutoRemove::SuggestsImportant=false
will cause all packages which were installed to be removed again, but as said,
it breaks recommends/suggests of packages (I guess there are some
recommends/suggests cycles here as well).

So, how am I able to reproduce this and/or are you sure nothing else on your
system recommends/suggests apache2 keeping it installed.

Also, does print
$ apt-mark showauto apache2
'apache2' or is the output empty?


The code for the autoremover is shared in libapt, so I would expect apt and
aptitude to have the same result, just that aptitude runs the autoremover by
default for all actions while it is an extra command in apt-get.


Best regards

David Kalnischkies

Attachment: signature.asc
Description: Digital signature


Reply to: