Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Matthias Klose Newsgroups: linux.debian.maint.python Subject: Re: Broken dbgsym packages for Python 3 Date: Mon, 04 Jun 2018 21:20:02 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Jun 4 19:16:26 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5 Old-X-Envelope-From: doko@debian.org User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Mailing-List: archive/latest/16009 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/6fed3179-ce15-75c7-4124-678a27b564c6@debian.org Approved: robomod@news.nic.it Lines: 23 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Mon, 4 Jun 2018 21:15:46 +0200 X-Original-Message-ID: <6fed3179-ce15-75c7-4124-678a27b564c6@debian.org> X-Original-References: <3475723.sHTRMIgmfr@kitterma-e6430> Xref: csiph.com linux.debian.maint.python:10603 On 04.06.2018 06:34, Scott Kitterman wrote: > On Sunday, June 03, 2018 09:26:58 PM Scott Talbert wrote: >> Hi, >> >> I've got a package (wxpython4.0) that builds modules for both Python 2.7 >> and Python 3. When I rebuilt the package in early May, I started getting >> the lintian warning debug-file-with-no-debug-symbols for the Python 3 >> dbgsym packages only. Sure enough, looking at those files, there is not >> much there. The Python 2.7 dbgsym files are fine. Given that I haven't >> changed anything in how the Python 3 modules are compiled, it seems that >> some outside change in the distribution has caused this. Has anyone else >> noticed this, or have any idea what might have caused these dbgsym >> packages to stop working? > > The -dbgsym packages don't work for Python anyway because you need to call the > debug interpreter, so I don't think it matters much either way. Usually the python*-*-dbg packages contain two things: - the unstripped extensions for the dbg interpreter - the debug symbols for the python*-* packages. If you don't have both of these, you should investigate why.