[Python-modules-team] Bug#700994: python3-numpy: directory vs. symlink conflict: /usr/include/python3.2
anbe at debian.org
Wed Feb 20 09:01:30 UTC 2013
while looking into #700782, we discovered that there is a symlink
vs. directory conflict between python3-numpy and python3.2-dev:
python3.2-dev has /usr/include/python3.2 -> python3.2mu
python3-numpy ships /usr/include/python3.2/numpy
Please move the linked shipped as python3.2/numpy to python3.2mu.
# apt-get install python3-numpy
# apt-get install python3-dev
Setting up python3.2-dev (3.2.3-6) ...
WARNING: non-empty directory on upgrade: /usr/include/python3.2
lrwxrwxrwx 1 root root 56 May 30 2012 numpy ->
Setting up python3-dev (3.2.3-5) ...
# ls -lad /usr/include/python*
drwxr-xr-x 2 root root 60 Feb 20 08:47 /usr/include/python3.2
drwxr-xr-x 2 root root 60 Feb 20 08:47 /usr/include/python3.2_d
drwxr-xr-x 2 root root 1900 Feb 20 08:47 /usr/include/python3.2mu
After fixing this in python3-numpy, please clone this a bug and
reassign to python3.2-dev to add an appropriate versioned Conflicts
against the buggy python-numpy3 versions. Breaks is probably not
sufficient to solve this "file conflict", as apt could decide to
deconfigure (and not upgrade) python3-numpy before
More information about the Python-modules-team