Hi all,
I was looking at splitting mpmath from sympy (with the help of the patches
from fedora) when I came across this at test time:
ebuild sympy-0.6.6.ebuild install
>>> Existing ${T}/environment for 'sympy-0.6.6' will be sourced. Run
>>> 'clean' to start with a fresh environment.
* sympy-0.6.6.tar.gz RMD160 SHA1 SHA256 size ;-) ...
[ ok ]
* checking ebuild checksums ;-) ...
[ ok ]
* checking auxfile checksums ;-) ...
[ ok ]
* checking miscfile checksums ;-) ...
[ ok ]
* checking sympy-0.6.6.tar.gz ;-) ...
[ ok ]
* Package: dev-python/sympy-0.6.6
* Repository: sage
* Maintainer: [email protected] [email protected]
* USE: elibc_glibc gtk ipython kernel_linux latex mathml opengl pdf png
userland_GNU x86
>>> It appears that 'sympy-0.6.6' is already setup; skipping.
>>> Remove '/var/tmp/portage/dev-python/sympy-0.6.6/.setuped' to force setup.
>>> Checking sympy-0.6.6.tar.gz's mtime...
>>> WORKDIR is up-to-date, keeping...
>>> It appears that 'sympy-0.6.6' is already prepared; skipping.
>>> Remove '/var/tmp/portage/dev-python/sympy-0.6.6/.prepared' to force
prepare.
>>> Configuring source in /var/tmp/portage/dev-
python/sympy-0.6.6/work/sympy-0.6.6 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-
python/sympy-0.6.6/work/sympy-0.6.6 ...
python2.6 setup.py build
Setting permissions of DOT_SAGE directory so only you can read and write it.
Traceback (most recent call last):
File "/usr/bin/sage-cleaner", line 25, in <module>
DOT_SAGE = os.environ['DOT_SAGE']
File "/usr/lib/python2.6/UserDict.py", line 22, in __getitem__
raise KeyError(key)
KeyError: 'DOT_SAGE'
Traceback (most recent call last):
File "/usr/bin/sage-cleaner", line 25, in <module>
DOT_SAGE = os.environ['DOT_SAGE']
File "/usr/lib/python2.6/UserDict.py", line 22, in __getitem__
raise KeyError(key)
KeyError: 'DOT_SAGE'
I get the same thing with sympy-0.6.7 from portage. I guess it only happens
when sage is already present so it would not be visible from a clean install
of sage. That sage being installed seem to have an influence on sympy further
merging is worrying. Some more packages could be affected (I tested mpmath
and there is no problem there).
Anyone else sees this?
This is with portage-2.2-rc97 that may have an influence.
Any idea for debuging this problem should it be real? ebuild --debug wasn't
helpful, I would need to run "python2.6 setup.py build -b build-2.6" with some
debug output.
Cheers,
Francois
