Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From: Scott Talbert <swt@techie.net>
Newsgroups: linux.debian.maint.python
Subject: Broken dbgsym packages for Python 3
Date: Mon, 04 Jun 2018 03:30:02 +0200
Message-ID: <vWMtQ-2jf-3@gated-at.bofh.it>
Old-Return-Path: <swt@techie.net>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Approved: robomod@news.nic.it
Lines: 13
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:10599

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?

Scott