Your message dated Sun, 6 May 2012 23:42:32 +0200
with message-id
<cab4xwxyibzegzb3pkacpwrar9owhyq0foszheqgkz7glfgn...@mail.gmail.com>
and subject line Re: [Python-modules-team] Bug#593662: python-numpy: dangling
symlinks
has caused the Debian Bug report #593662,
regarding python-numpy: dangling symlinks
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
593662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593662
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-numpy
Version: 1:1.4.1-4
Severity: minor
>From the debian changelog:
python-numpy (1:1.4.1-3) unstable; urgency=low
* debian/rules
- use the python-support specific directory (/usr/lib/pymodules) for the
symlinks /usr/include/python*/numpy; this correctly installs the header
files (mainly _numpyconfig.h) used by depending packages; Closes: #589592
Nice and easy solution, but it introduces dangling symlinks for each
python version not installed:
[10]matica:~# symlink_check -m M,L,D,R / /usr/local /var
D:/usr/include/python2.5/numpy ->
../../lib/pymodules/python2.5/numpy/core/include/numpy
D:/usr/include/python2.5_d/numpy ->
../../lib/pymodules/python2.5/numpy/core/include/numpy
[11]matica:~# dpkg --list 'python2.[0-9]'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-====================-====================-========================================================
un python2.4 <none> (no description available)
un python2.5 <none> (no description available)
ii python2.6 2.6.6~rc1-1 An interactive high-level
object-oriented language (vers
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.34.4-core2-ii (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python-numpy depends on:
ii libatlas3gf-base [liblapack.s 3.6.0-24 Automatically Tuned Linear Algebra
ii libatlas3gf-sse2 [liblapack.s 3.6.0-24 Automatically Tuned Linear Algebra
ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib
ii libgcc1 1:4.4.4-8 GCC support library
ii libgfortran3 4.4.4-8 Runtime library for GNU Fortran ap
ii python 2.6.5-11 interactive high-level object-orie
ii python-support 1.0.9 automated rebuilding support for P
python-numpy recommends no packages.
Versions of packages python-numpy suggests:
pn gfortran <none> (no description available)
ii python-dev 2.6.5-11 header files and a static library
pn python-nose <none> (no description available)
pn python-numpy-dbg <none> (no description available)
pn python-numpy-doc <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
tags 593662 +wontfix
thanks
On Wed, Dec 22, 2010 at 8:59 PM, Sandro Tosi <[email protected]> wrote:
> Hi Ian,
>
> On Fri, Aug 20, 2010 at 07:07, Ian Zimmerman <[email protected]> wrote:
>> Package: python-numpy
>> Version: 1:1.4.1-4
>> Severity: minor
>>
>>
>> >From the debian changelog:
>>
>> python-numpy (1:1.4.1-3) unstable; urgency=low
>>
>> * debian/rules
>> - use the python-support specific directory (/usr/lib/pymodules) for the
>> symlinks /usr/include/python*/numpy; this correctly installs the header
>> files (mainly _numpyconfig.h) used by depending packages; Closes:
>> #589592
>>
>> Nice and easy solution, but it introduces dangling symlinks for each
>> python version not installed:
>
> Yes, that's because it creates symlinks for all the supported python
> versions, so the non-default version can also be not installed, hence
> generating dangling symlinks.
>
> How would you resolve the problem that when installing a supported
> version after having installed python-numpy, those symlinks have to be
> there?
Well, I don't know how to properly create those symlinks when a
supported python version gets installed, nor if it's really worth the
effort.
I'm closing this report (on the long rung, we'll have just one python
2.x and python3.x share the same directory).
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
_______________________________________________
Python-modules-team mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
