Hi Christian, On Montag, 23. März 2015, Christian Kastner wrote: > I'm having problems reproducing this. I just tried upgrading in pristine > wheezy VMs > (a) with libcap2-bin > (b) with libcap2-bin + libpam-cap installed, > > and I didn't encounter this issue.
hm, interesting. It also only shows up on some upgrade tests, but not all: https://jenkins.debian.net/view/chroot-installation/view/Problems/ while most of these went fine: https://jenkins.debian.net/view/chroot-installation/view/upgrade%20wheezy2jessie/ (There are full logs available for download...) > OK, but in this case, we don't have libcap2-bin, but libcap2-bin + > libpam-cap instead. I'm not sure how to parse this, as the combination of the two is exactly what I've identified as problematic. > This is the part that puzzles me. capability.conf only gets > rm_conffile'd in the most recent version, but in none of my tests > does this trigger the above. I think it's also a question of ordering: if libpam-cap is updated first and and libcap2-bin is removed second, things go well. If libcap2-bin is removed first and libpam-cap second, you will encounter the problem. cheers, Holger
signature.asc
Description: This is a digitally signed message part.
