package: libcap2-bin version: 1:2.24-7 severity: serious x-debbugs-cc: p...@debian.org
Hi,
to fix #768229 ("conffile not removed"), you added code to do that in the
postinst script of libcap2-bin. Unfortunatly, this confile is owned by libpam-
cap nowaways, and thus upgrades from wheezy to jessie now get a missing
/etc/security/capability.conf file and thisquestion during upgrades:
Setting up libpam-cap:amd64 (1:2.24-7) ...
Configuration file `/etc/security/capability.conf'
==> Deleted (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** capability.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing libpam-
cap:amd64 (--configure):
I've seen this in several jenkins jobs, eg
https://jenkins.debian.net/job/chroot-installation_wheezy_install_education-
development_upgrade_to_jessie/63//console but also
https://jenkins.debian.net/job/chroot-
installation_wheezy_install_lxde_upgrade_to_jessie/562//console and
https://jenkins.debian.net/job/chroot-
installation_wheezy_install_full_desktop_upgrade_to_jessie/567//console
Also see https://packages.debian.org/sid/amd64/libpam-cap/filelist
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
