Re: -dbg packages
[Jakub Wilk, 2011-08-10]
> Added to my "Why You Should Stay Away From Dh_Python2" list, thanks.
can I see that list? (dh_python2 has been already improved a lot thanks
to your bug reports)
> >>>and adds dependencies to ${python:Depends}, yes
> >>What exactly it puts into python:Depends? I know it puts -dbg
> >>interpreter there, but what about stuff from requires.txt?
> >requires.txt is removed (as all other files in .egg-info) so there's
> >nothing to add
>
> I hope you are all aware, that if python-dbg tries to import foo, and
> foo_d.so is not found, it'll try to load foo.so instead (and then
> it'll fail with a very obscure error message). So it's quite
yeah, we should file a bug upstream to fix this error message
(the first thing I say when someone points me to it is: "did you install
-dbg package for this extension?")
> important to keep your bar-dbg's Depends/Recommends line correct. And
> you have to do it manually (which is not bad per se), even when bar's
> Depends line is automatically generated from requires.txt.
the problem is I have no idea if Baz should be translated to
python-baz-dbg or skipped (as python-bar already depends on python-baz)
i.e. if Baz is a pure Python module or an extension, so I cannot use
requires.txt data anyway (crazy idea: Provide: python-foo-dbg packages
in packages with pure Python foo modules and no extensions)
> >>Also, it means that you should use "Recommends:
> >>${python:Depends}" for your -dbg package. Yay.
> >
> >why?
>
> Because otherwise you'll end up with "Depends: python-dbg" which is
> too strict. See http://wiki.debian.org/Python/DbgBuilds for
> rationale.
it actually generates python2.X-dbg | python2.Y-dbg (and python-dbg (>=
2.X), python-dbg (<< 2.Y+1) which you requested due to transitions issues)
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Reply to: