On Sun, Oct 31, 2010 at 03:42:29PM +0100, Lucas Nussbaum wrote: > Package: cyrus-sasl2-heimdal-dbg > Version: 2.1.23.dfsg1-6 > Severity: serious > > Hi, > > Installing cyrus-sasl2-heimdal-dbg in a lenny chroot, then upgrading to > squeeze, causes: > Preparing to replace cyrus-sasl2-heimdal-dbg 2.1.22.dfsg1-23+lenny1 (using > .../cyrus-sasl2-heimdal-dbg_2.1.23.dfsg1-6_amd64.deb) ... > Unpacking replacement cyrus-sasl2-heimdal-dbg ... > Preparing to replace cyrus-sasl2-dbg 2.1.22.dfsg1-23+lenny1 (using > .../cyrus-sasl2-dbg_2.1.23.dfsg1-6_amd64.deb) ... > Unpacking replacement cyrus-sasl2-dbg ... > dpkg: error processing > /var/cache/apt/archives/cyrus-sasl2-dbg_2.1.23.dfsg1-6_amd64.deb (--unpack): > trying to overwrite '/usr/lib/debug/usr/lib/sasl2/libgssapiv2.so.2.0.23', > which is also in package cyrus-sasl2-heimdal-dbg 2.1.23.dfsg1-6 > configured to not write apport reports > dpkg-deb: subprocess paste killed by signal (Broken pipe) > I'd be interested to know if anyone has a recommendation on how to handle this. The two packages in question are -dbg packages that are created by dh_strip, excerpted from debian/rules below:
dh_strip -s -psasl2-bin -plibsasl2-2 -plibsasl2-modules -plibsasl2-modules-ldap -plibsasl2-modules-otp -plibsasl2-modules-sql -plibsasl2-modules-gssapi-mit -plibsasl2-dev -Nlibsasl2-modules-gssapi-heimdal --dbg-package=cyrus-sasl2-dbg dh_strip -s -plibsasl2-modules-gssapi-heimdal -Nsasl2-bin -Nlibsasl2-2 -Nlibsasl2-modules -Nlibsasl2-modules-ldap -Nlibsasl2-modules-otp -Nlibsasl2-modules-sql -Nlibsasl2-modules-gssapi-mit -Nlibsasl2-dev --dbg-package=cyrus-sasl2-heimdal-dbg Both packages need to be able to be installed together, so my question centers around whehter it is OK to put a diversion in place so that cyrus-sasl2-heimdal-dbg diverts the file. What does everyone think? Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
signature.asc
Description: Digital signature
