Re: Veusz - update to 3.0
Hi Jeremy, On Sun, Jun 17, 2018 at 12:11:04PM +0200, Jeremy Sanders wrote: > [...] > > Another issue is that I can't get continuous integration tests working > properly on Salsa. The module works fine in a pbuilder build, but on Salsa, > Qt can't load its xcb module for the self tests under Xvfb. I forked your repository and added QT_DEBUG_PLUGINS=1 before the failing command. Looks like the process is running out of memory: https://salsa.debian.org/mitya57/veusz/-/jobs/31240 I do not know what to do with this, but at least we now know the reason. -- Dmitry Shachnev signature.asc Description: PGP signature
Request to join the Python Modules team
Hi, I would like to join the Salsa Python Modules team in order to continue maintaining my package python-gmpy2. I previously had Alioth access and have finally had time to migrate to Salsa. My Salsa login is aomighty-guest. I have attempted to read and accept the Python Modules policy (https://python-modules.alioth.debian.org/python-modules-policy.html), as stated in https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin, but the link is dead. Thanks, Martin
Re: Request to join the Python Modules team
[Martin Kelly, 2018-07-15] > I would like to join the Salsa Python Modules team in order to continue > maintaining my package python-gmpy2. I previously had Alioth access and have > finally had time to migrate to Salsa. > > My Salsa login is aomighty-guest. done -- GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
How to convince ‘dh_python3’ to handle ‘/usr/lib/python3.7/dist-packages/foo.egg-info/’ correctly?
Howdy all, The ‘python-coverage’ source package has some special handling of build and install rules. How can I convince the packaging tools to correctly handle ‘/usr/lib/python3.7/dist-packages/foo.egg-info/’? This was brought to my attention by the recent addition of the Lintian tag “python-module-in-wrong-location”: W: python3-coverage: python-module-in-wrong-location usr/lib/python3.7/dist-packages/coverage-4.5.1.egg-info/ usr/lib/python3/dist-packages/coverage-4.5.1.egg-info/ N: N:The package installs a Python module or debug information for a Python N:module in the wrong location for the given version of Python. N: N:dh_python3 can be used to fix this for Python 3 modules. N: N:Refer to Debian Python Policy section 2.5 (Module Path) and N:https://bugs.debian.org/576012 for details. N: N:Severity: normal, Certainty: possible N: N:Check: files, Type: binary, udeb N: W: python3-coverage: python-module-in-wrong-location usr/lib/python3.7/dist-packages/coverage-4.5.1.egg-info/entry_points.txt usr/lib/python3/dist-packages/coverage-4.5.1.egg-info/entry_points.txt Which particular of those files are right or wrong, according to the Debian Python Policy §2.5? * usr/lib/python3.7/dist-packages/coverage-4.5.1.egg-info/ * usr/lib/python3/dist-packages/coverage-4.5.1.egg-info/ * usr/lib/python3.7/dist-packages/coverage-4.5.1.egg-info/entry_points.txt * usr/lib/python3/dist-packages/coverage-4.5.1.egg-info/entry_points.txt How should I change the package's ‘debian/rules’ to conform to Debian Python Policy §2.5? -- \“I went to the hardware store and bought some used paint. It | `\ was in the shape of a house.” —Steven Wright | _o__) | Ben Finney
