Please add my DD account to the Salsa group
Hello I'm already a member of DPMT and in the salsa group with my valhalla-guest account. I now have a DD account (valhalla) and I would like to start using it instead. I couldn't find what is the proper procedure to do so, could somebody point me to the right documentation? If the right procedure is to ask on the list, instead, can somebody please add me? I already accepted the policy back when I joined, and I've just re-read it on https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst -- Elena ``of Valhalla'' signature.asc Description: PGP signature
Re: Joining DPMT
[Willem van den Akker, 2018-05-31] > I am maintaining python-ldap and want to make it a team-package. > My login name: wvdakker-guest > I have read and accept the Debian Python Modules Team - Policy on > salso (there is in invalid link to alioth in the document). > > A 3.10 package is available on mentors (https://mentors.debian.net/pack > age/python-ldap). I will submit a sponsor request on IRC. welcome :) -- GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Re: Broken dbgsym packages for Python 3
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
Broken dbgsym packages for Python 3
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