Control: tag -1 + moreinfo
Hi Holger,
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.
On 2015-03-23 21:06, Holger Levsen wrote:
> 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
if _only_ libcap2-bin is installed, then /etc/security/capability.conf
is superfluous, so this shouldn't be an issue.
> and thisquestion during upgrades:
>
> Setting up libpam-cap:amd64 (1:2.24-7) ...
OK, but in this case, we don't have libcap2-bin, but libcap2-bin +
libpam-cap instead.
> Configuration file `/etc/security/capability.conf'
> ==> Deleted (by you or by a script) since installation.
> ==> Package distributor has shipped an updated version.
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'll need to investigate some more...
Regards,
Christian
> 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):
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
