Hi
On 2015-04-28 12:20:32, Dmitry Shachnev wrote:
I have noticed that my python3-sip4-dbg package does not have debug symbols
for the python3 extension (i.e. sip.cpython-34m-x86_64-linux-gnu.so).
That package does not use distutils/setuptools, but uses its own build
system instead. In
Hello, -python
I'd like to contribute to debian and be a part of Python Modules
Packaging Team. As my way in, I'd like to adopt python-simpy, maintained
by Nicolas Dandrimont in the past. I uploaded a new version of the
package with Simpy's new release on mentors.debian.net and Nicolas is
going
Hi,
On Mon, 27 Apr 2015 10:20:05 +0800, mudongliang wrote:
Today I try to install a software - youdao dict.
First I try it in vmware machine: Linuxmint and Ubuntu. It can succeed!
But when I do it in Debian , it fails ; And the reason is the lost of
python3-xlib.
So I search in the web page
Hi Sebastian,
On Sat, 2 May 2015 12:42:13 +0200, Sebastian Ramacher wrote:
You could bump compat to 9 and use debug symbol files based on the build id.
This should circumvent any filename based problems.
That indeed helped, thanks!
--
Dmitry Shachnev
signature.asc
Description: OpenPGP
Control: retitle -1 ITP: mistune -- markdown parser in pure python
Hi,
I'm willing to work on packaging it. I'm not part of the debian python
modules team yet, but I'm willing to.
I'm part of the debian-science team already, so I do have some
experience packaging for debian.
Snark on
On Sat, 2 May 2015, Robert Collins wrote:
This still seems like a profoundly poor idea: 'is X python3
compatible' is a turing completeness problem. There are some scripts
where you can determine compatibility, but many where you cannot until
it blows up (particularly ones with subtle bugs in
6 matches
Mail list logo
