when rebuilding a local package that iterates on
"py3versions -s" (that just gained python3.7 in addition to python3.6)
Will the python3-numpy pacakge be fixed by an automatic rebuild ?
(ie I just have to wait for a few days)
Do I need to fill a bug report on python3-numpy ?
Reg
it.
Regards,
Vincent
--
Vincent Danjean GPG key ID 0x9D025E87 vdanj...@debian.org
GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87
Unofficial pacakges: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo: deb http://perso.debian.org/~vdanjean
after the
lenny freeze)
For myself, I'm using git (with git-svn) to maintain mercurial with
branches for backport. If you want to take over (or even help with)
this package, I will send you all my works.
Regards,
Vincent
Thanks!
Vernon
--
Vincent Danjean GPG key ID 0x9D025E87
Hi,
I'm the maintainer of mercurial. At least one of the users has a
problem with loading python modules.
Can someone look at bug #382252 ?
In short,
echo 'import sys; print sys.path; from mercurial import bdiff' | python2.4
works on my system, but not on its one.
Both have
Josselin Mouette a écrit :
mdiff.py does import bdiff which looks for bdiff.so in the same
directory. On your system, mdiff.py is is
in /var/lib/python-support/python2.4/mercurial/ which is the correct
place for packages handled by python-support, while on the user's system
it is in
Wouter Cloetens a écrit :
On Wed, Jan 03, 2007 at 01:04:37PM +0100, Pierre Habouzit wrote:
To Wouter: to resolve your problem, just rm -rf
/usr/lib/python*/site-packages/mercurial. You can do that safely,
that'll solve your problem.
Success! Many thanks!
You need to remove
Steve Langasek a écrit :
On Wed, Jan 03, 2007 at 01:04:37PM +0100, Pierre Habouzit wrote:
he does not needs to, having run hg as root is enough to produce the
*.pyc if your package (even against the previous policy) did not managed
them.
Um, isn't this only the case if the user was
Josselin Mouette wrote:
Le mardi 04 juillet 2006 à 09:25 +0200, Vincent Danjean a écrit :
What would be the interest for an application to be present (compiled)
several times on the same system ?
This is the whole point of the new policy. It allows for several python
versions
Hi,
I'm converting one of my package (commit-tool) to the new policy.
I was thinking it will be easy, but I found several difficulties.
I'm able to deal with them so that I will be conformed to the new
policy, but I would like to do the Right Things.
Here is the situation.
My package has
Raphael Hertzog wrote:
On Tue, 13 Jun 2006, Raphael Hertzog wrote:
Here's a list of sources packages that need to be updated (266 packages):
http://people.debian.org/~hertzog/python/sources-by-maint
Pierre Habouzit (Madcoder) did the mass-bug filing:
http://bugs.debian.org/submitter:[EMAIL
10 matches
Mail list logo
