Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From: Scott Kitterman <debian@kitterman.com>
Newsgroups: linux.debian.maint.python
Subject: Re: Broken dbgsym packages for Python 3
Date: Mon, 04 Jun 2018 06:40:01 +0200
Message-ID: <vWPrH-49x-1@gated-at.bofh.it>
References: <vWMtQ-2jf-3@gated-at.bofh.it>
Old-Return-Path: <debian@kitterman.com>
User-Agent: KMail/4.13.3 (Linux/3.13.0-147-generic; KDE/4.13.3; x86_64; ; )
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Approved: robomod@news.nic.it
Lines: 17
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:10600

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.

Scott K