On 2015-03-13 23:49, Christian Kastner wrote:
>>> Would you by chance be available for sponsoring? (No problem if not, but
>>> if yes, please wait for an updated debdiff as the RT approved another
>>> one-line fix.)
I'm not sure that this is the correct approach for capability.conf -
it's not an obsolete conffile, it has moved to libpam-cap instead (which
it Recommends)
The rm_conffile is fine as long as libpam-cap is not installed, but I'm
not sure whether this runs smoothly if libpam-cap is upgraded at the
same time ...
I even added some workarounds in piuparts for a related issue (a
conffile was disappearing sometimes, but never from the reference
chroot) - since I didn't really see a fault in your packages:
case ${PIUPARTS_OBJECTS%%=*} in
kismet|\
tshark|\
wireshark|\
wireshark-common|\
wireshark-dbg|\
libcap2-bin)
# libcap2-bin/wheezy is part of the minimal
chroot and recommends libpam-cap
# a conffile moved from libcap2-bin/squeeze to
libpam-cap/wheezy
log_debug
apt-get install -yf libpam-cap
;;
That said, the versioning in the maintscript is wrong as well. This
needs to be the version where the rm_conffile call was added (plus
suffix '~', so it is "before" the current version), not the version that
stopped shipping the conffile. Ideally both versions are the same. But
since this isn't even a normal removal ...
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
