PING: mercurial: Fixing quilt dependency

[I posted this a few months ago, but no one responded. Reposting.] Hi Vincent (and others), Regarding your change to the mercurial packaging: +mercurial (1.3.1-2) UNRELEASED; urgency=low + + * adjust quilt dependency so that it works with backports +(ie quilt >> 0.46-6 instead of quilt >= 0

mercurial: python-docutils builddep should? be (>= 0.5)

Mercurial 1.4 adds a builddep on python-docutils, which has been added in PAPT svn. Owing to the use of --strip-elements-with-class, this actually requires >= 0.5. Given that 0.5 is already present in all but oldstable, I'm not sure whether the builddep _should_ be changed, but I would imagine bac

mercurial: Fixing quilt dependency

Hi Vincent (and others), Regarding your change to the mercurial packaging: +mercurial (1.3.1-2) UNRELEASED; urgency=low + + * adjust quilt dependency so that it works with backports +(ie quilt >> 0.46-6 instead of quilt >= 0.46-7) + + -- Vincent Danjean Tue, 18 Aug 2009 12:44:51 +0200 +

Is /usr/share/python/runtime.d/ documented?

Hi, Is the /usr/share/python/runtime.d/ interface documented anywhere? Or is the only "documentation" reading the sourcecode of the python-defaults package? Thanks, Max. signature.asc Description: OpenPGP digital signature

Re: Existing modules for new Python

anatoly techtonik wrote: > Hello, > > Can anybody tell what happens with existing Python modules when a new > Python version is deployed on the system? > Are they recompiled or reinstalled or left inaccessible in this version? Debian python packages trigger hook scripts in /usr/share/python/runti

Re: SONAME for python modules is bad?

Steve M. Robbins wrote: > A cc is appreciated as I don't subscribe to debian-python. > >> On Wed, Jul 22, 2009 at 8:47 AM, Steve M. Robbins wrote: >> > Hi, >> > >> > Recently, Mathieu Malaterre wrote to say that having a SOVERSION on a >> > python module is wrong, with reference to an oblique comm