(I wish we could just have automated debug packages and don't have to
worry about this... :/)
* Helmut Grohne <hel...@subdivi.de>, 2013-01-09, 09:53:
weasel noted that tor-dbg exists and depends on tor. Since dpkg
currently handles arch all packages as if they were native for
dependency resolution [1], this leads to this situation:
* tor-dbg requires tor to be installed for the same arch as tor-dbg.
Can you give a technical reason for this? Why would taking a core file
on a different system and debugging it with just the tor-dbg image
using gdb-multiarch not work?
Are you saying that "tor-dbg" should not depend on "tor" at all?
Well, that's not unreasonable, but that's also not what we've been
historically doing with -dbg packages[0].
But _if_ "tor-dbg" is supposed to depend "tor", then marking tor as
MA:foreign is clearly wrong.
Indeed it should be possible to turn tor-dbg into Multi-Arch:same with
some more effort (i.e. not for wheezy).
True, but I don't see how is this relevant for the problem at hand.
According to [2] and in theory, the fix for this bug is:
Package: tor
Architecture: any
Depends: ...
Multi-Arch: allowed
We should notice that Multi-Arch:allowed was not intended for this
case. "Abusing" allowed here just for a debug dependency sounds just
wrong.
It doesn't to me.
So what are other packages doing?
avahi-daemon is M-A:foreign. avahi-dbg has no dependencies.
bluez is M-A:foreign. bluez-dbg depends on bluez (= ${binary:Version}).
cmake is M-A:foreign. cmake-dbg depends on cmake (= ${binary:Version}).
cups is M-A:foreign. cups-dbg depends on cups (= ${binary:Version}).
daisy-player is M-A:foreign. daisy-player-dbg depends on daisy-player
(= ${binary:Version}).
dbus is M-A:foreign. dbus-1-dbg depends on dbus (= ${binary:Version}).
e2fsprogs is M-A:foreign. e2fsprogs depends on e2fsprogs
(= ${binary:Version}).
ebook-speaker is M-A:foreign. ebook-speaker-dbg depends on ebook-speaker
(= ${binary:Version}).
espeak is M-A:foreign. espeak-dbg depends on espeak
(= ${binary:Version}).
ghostscript is M-A:foreign. ghostscript-dbg seems to be a cumulative
debug package. One alternative of the dependencies is ghostscript
(= ${binary:Version}).
gpsd is M-A:foreign. gpsd-dbg seems to be a cumulative debug package.
One alternative of the dependencies is gpsd (= ${binary:Version}).
imagemagick is M-A:foreign. imagemagick-dbg depends on imagemagick
(= ${binary:Version}).
I believe we can already spot a pattern.
I can see a pattern of bugs. :)
[0] http://lintian.debian.org/tags/dbg-package-missing-depends.html
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
