Groups > linux.debian.maint.python > #10599

Broken dbgsym packages for Python 3

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> (permalink)
X-Original-To	debian-python@lists.debian.org
X-Mailbox-Line	From debian-python-request@lists.debian.org Mon Jun 4 01:27:17 2018
Old-Return-Path	<swt@techie.net>
X-Amavis-Spam-Status	No, score=-7.1 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -6.1
Dkim-Signature	v=1; a=rsa-sha256; c=simple/simple; d=techie.net; s=default; t=1528075618; bh=SWLpvIZjLOhRwaHtbKUB9QK7RXHztvno4+mqdqcPVpo=; h=Date:From:To:Subject:From; b=pC5x2aZfROHODeG6QGCT7sNTaV4KIg5sTc/QRXntHQhpkV5z72anhPYMSWqMq+PB4 pYQlk2wDoZEN09W7+FOhTCde0AUAPRhuiwOVysEvIoonN6zBxpB/XJqEcAatso7cUe c6mhwm7LrXSk/OGe90Nuao9Yx23grIRJrgEyTGek=
X-X-Sender	talbert@bear.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
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/16005
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/alpine.DEB.2.20.1806032119350.9990@bear.techie.net
Approved	robomod@news.nic.it
Lines	13
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Sun, 3 Jun 2018 21:26:58 -0400 (EDT)
X-Original-Message-ID	<alpine.DEB.2.20.1806032119350.9990@bear.techie.net>
Xref	csiph.com linux.debian.maint.python:10599

Show key headers only | View raw

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

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Broken dbgsym packages for Python 3 Scott Talbert <swt@techie.net> - 2018-06-04 03:30 +0200
  Re: Broken dbgsym packages for Python 3 Scott Kitterman <debian@kitterman.com> - 2018-06-04 06:40 +0200
    Re: Broken dbgsym packages for Python 3 Matthias Klose <doko@debian.org> - 2018-06-04 21:20 +0200
      Re: Broken dbgsym packages for Python 3 Scott Talbert <swt@techie.net> - 2018-06-05 06:20 +0200
        Re: Broken dbgsym packages for Python 3 Andrey Rahmatullin <wrar@debian.org> - 2018-06-05 07:50 +0200
          Re: Broken dbgsym packages for Python 3 Scott Talbert <swt@techie.net> - 2018-06-05 15:20 +0200

csiph-web