Vincent Bernat <ber...@debian.org> writes: >>> I don't think that python-all-dbg and python3-all-dbg will be needed >>> to build the package. > >> To build the debug versions, I'm calling python-dbg setup.py (so I need >> python-*-dbg). Is that the wrong thing to do? > > I was not aware that this was the way to do it.
I don't know any other way to build the extension for the debug compiler, but if you tell me one then I'll be happy to use it :-). Otherwise it seems to me that I really need the dependency on python-all-dbg. >>> The python3-llfuse-dbg does not contain debug symbols. Only the debug >>> version of the library (llfuse.cpython-32dmu.so). > >> I'm a bit at a loss here. For some reason, dh_strip puts the >> python3-llfuse debugging symbols into the python-llfuse-dbg directory: > >> $ dh_strip -v -a -ppython-llfuse --dbg-package=python-llfuse-dbg >> [...] >> Shouldn't this command only work on the python-llfuse package? > > The "-a" means "all arch packages". I suppose that you should not use it > with "-p". Ah, of course. This should be fixed as well now. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/871uyx5stf....@inspiron.ap.columbia.edu
