(I'm aware I'm digging up a decade-old bug, but I happened to see it
while checking whether #926191 was already open.)
On Thu, 04 Sep 2008 at 19:25:05 +0200, Goswin von Brederlow wrote:
> I think zlib1g-dbg should have
>
> Depends: lib64z1 (= 1:1.2.3.3.dfsg-12)
>
> to ensure that it will always match the version exactly. Without that
> the lib64z1 can be uninstalled (which doesn't hurt as then you would
> not have anything to debug) or more importantly have a different
> version.
10 years later, in the glorious(?) multiarch future, I think the vast
majority of users of zlib1g-dbg should only be interested in zlib1g, not
lib64z1. To avoid the mismatched version, I'd suggest either migrating to
the automatically-generated -dbgsym packages (see "Alternatively..." in
#926191), or using something like this:
Package: zlib1g-dbg
Depends: zlib1g (= ${binary:Version})
Breaks: lib64z1 (<< ${binary:Version}), lib64z1 (>> ${binary:Version})
smcv
