Your message dated Tue, 12 May 2020 14:33:05 +0100
with message-id <20200512133305.GA1433342@horizon>
and subject line Re: Bug#926191: zlib1g-dbg: please mark zlib1g-dbg as
Multi-Arch: same
has caused the Debian Bug report #926191,
regarding zlib1g-dbg: please mark zlib1g-dbg as Multi-Arch: same
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
926191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926191
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: zlib1g-dbg
Version: 1:1.2.11.dfsg-1
Severity: wishlist
It looks as though zlib1g-dbg packages from multiple architectures can be
installed in parallel without collisions (all filenames outside /usr/share
are hash-based). In a future upload please consider adding Multi-Arch: same:
Package: zlib1g-dbg
Multi-Arch: same
(etc.)
This should be enough to allow these detached debug symbols to be used to
debug 32- and 64-bit programs, native and cross programs, etc. without
removing one architecture's package and installing another.
Alternatively, you could remove the zlib1g-dbg package from d/control
and change
dh_strip -s --dbg-package=zlib1g-dbg
to
dh_strip -s --dbgsym-migration="zlib1g-dbg (<< X~)"
where X is the version number in which you made that change. This
would result in zlib1g-dbgsym, lib64z1-dbgsym, etc. packages with
Conflicts/Replaces on zlib1g-dbg (<< X~) being generated mechanically by
debhelper and placed in the http://deb.debian.org/debian-debug lookaside
repository by dak, and zlib1g-dbgsym would inherit the Multi-Arch: same
field from zlib1g. (This is supported since stretch, and does not
require going through the NEW queue, unlike most new binary packages.)
For some context for this request, I'm trying to build a self-contained
biarch 32- and 64-bit "SDK" runtime environment with development files
and debug symbols for a whole stack of packages, and I was pleased to
find that this is mostly possible already: zlib1g was one of only a few
libraries in my stack where I can install debug symbols for one word-size
but not the other at the same time.
smcv
--- End Message ---
--- Begin Message ---
Version: 1:1.2.11.dfsg-2
On Mon, 01 Apr 2019 at 19:41:43 +0100, Simon McVittie wrote:
> Alternatively, you could remove the zlib1g-dbg package from d/control
> and change
>
> dh_strip -s --dbg-package=zlib1g-dbg
>
> to
>
> dh_strip -s --dbgsym-migration="zlib1g-dbg (<< X~)"
>
> where X is the version number in which you made that change. This
> would result in zlib1g-dbgsym, lib64z1-dbgsym, etc. packages with
> Conflicts/Replaces on zlib1g-dbg (<< X~) being generated mechanically by
> debhelper
This change was made in version 1:1.2.11.dfsg-2, which resolves this bug.
On Wed, 30 Oct 2019 at 17:10:38 +0000, Witold Baryluk wrote:
> $ sudo apt-get install -V zlib1g-dbg:amd64 zlib1g-dbg:i386
In testing/unstable, zlib1g-dbg no longer exists, but you can install
zlib1g-dbgsym:amd64 and zlib1g-dbgsym:i386 together.
smcv
--- End Message ---
