Re: Broken dbgsym packages for Python 3

2018-06-05 Thread Scott Talbert
On Tue, 5 Jun 2018, Andrey Rahmatullin wrote: Yes, I'm talking about the automatically generated -dbgsym packages that contain the /usr/lib/debug/.build-id/... files. Have you read Scott's email? Yes, but wouldn't they still be useful for symbolicating core dumps? Scott

Re: Broken dbgsym packages for Python 3

2018-06-04 Thread Andrey Rahmatullin
On Tue, Jun 05, 2018 at 12:11:21AM -0400, Scott Talbert wrote: > Yes, I'm talking about the automatically generated -dbgsym packages that > contain the /usr/lib/debug/.build-id/... files. Have you read Scott's email? -- WBR, wRAR signature.asc Description: PGP signature

Re: Broken dbgsym packages for Python 3

2018-06-04 Thread Scott Talbert
On Mon, 4 Jun 2018, Matthias Klose wrote: 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, l

Re: Broken dbgsym packages for Python 3

2018-06-04 Thread Matthias Klose
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-deb

Re: Broken dbgsym packages for Python 3

2018-06-03 Thread Scott Kitterman
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