Your message dated Fri, 02 May 2014 12:35:58 +0000
with message-id <[email protected]>
and subject line Bug#740406: Removed package(s) from unstable
has caused the Debian Bug report #635896,
regarding automake1.10: AM_PATH_PYTHON: ${prefix}/lib/python2.?/{site, 
dist}-packages/ detected wrong for Python 2.6+
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.)


-- 
635896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635896
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: automake1.10
Version: 1:1.10.3-1
Severity: normal

AM_PATH_PYTHON from /usr/share/aclocal-1.10/python.m4 doesn't return the
right directory for Python 2.6 extensions on Debian: It returns
${prefix}/lib/python2.[67]/site-packages/ instead of .../dist-packages/.

This is because of /usr/share/aclocal-1.10/python.m4:98
  AC_SUBST([PYTHON_PREFIX], ['${prefix}'])
which defines PYTHON_PREFIX as the un-expanded string '${prefix}'
Notice that this is quoted and does not get expanded!

This then gets passed to /usr/share/aclocal-1.10/python.m4:120
    [am_cv_python_pythondir=`$PYTHON -c "from distutils import sysconfig; print 
sysconfig.get_python_lib(0,0,prefix='$PYTHON_PREFIX')" 2>/dev/null ||
     echo "$PYTHON_PREFIX/lib/python$PYTHON_VERSION/site-packages"`])
which then calls Python with the unexpanded '${prefix}'

/usr/lib/python2.6/distutils/sysconfig.py:110 just checks the prefix for
/usr and /usr/local, but not for '${prefix}', thus returning
'.../site-packages' instead of '.../dist-packages'

See the difference when calling it directly from commandline:
  /usr/bin/python2.6 -c 'from distutils import sysconfig; print 
sysconfig.get_python_lib(0,0,prefix="${prefix}")'
    ${prefix}/lib/python2.6/site-packages
  /usr/bin/python2.6 -c 'from distutils import sysconfig; print 
sysconfig.get_python_lib(0,0,prefix="/usr")'
    /usr/lib/python2.6/dist-packages
(I switch ' and " for easier shell quoting)

dh_python2 later complains about the wrong directory, but moves the
files to the right directory, so this is currently not critical.

It would be nice if the interaction between python.m4 and
python/distutils/sysconfig.py could be fixed. I'm unsure if this is
acrually a bug in autoconf or python.
-- System Information:
Debian Release: 6.0.2
  APT prefers stable
  APT policy: (990, 'stable'), (90, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages automake1.10 depends on:
ii  autoconf                  2.67-2         automatic configure script builder
ii  autotools-dev             20100122.1     Update infrastructure for config.{
ii  dpkg                      1.15.8.11      Debian package management system
ii  install-info              4.13a.dfsg.1-6 Manage installed documentation in 

automake1.10 recommends no packages.

automake1.10 suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 1:1.10.3-3.1+rm

Dear submitter,

as the package automake1.10 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/740406

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to