Your message dated Sat, 24 Feb 2007 12:17:02 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#397895: fixed in python-support 0.6.1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: python-support Version: 0.5.4 Severity: important Hi, (Documenting a conversation I had with the python-support maintainer and another I had with Steinar H. Gunderson on IRC.) By design, python-support might break some applications. Two examples lately were the GStreamer 0.10 Python bindings and the GNOME Deskbar Applet. This is usually because these packages are ./configured with a default Python path, such as /usr/lib/pythonX.Y/site-packages where the upstream package expects to find it's *.py and *.pyc files after the installation (IOW, at runtime), but dh_pysupport moves the *.py to /usr/share/python-support and byte compiles them into *.pyc files below /var/lib/python-support. One workaround is to patch the upstream code to deal with this situation; this can be complex because upstream might not make any difference between the path to *.py files and the path to *.pyc files. The AM_PATH_PYTHON macro understands the difference, but does not permit changing these. Another workaround is to use python-central. Some random thoughts on the issue: 1) I am not too sure that python-support truly needs to adhere to the FHS since it is only invoked on package installation / upgrades and can be considered part of "package management". 2) I think *.pyc are arch independent and are supposed to stay that way, this means that we could have *.pyc under /usr, python-support could byte-compile unser /usr/share/python-support, hence we could ./configure with this python-path, and we would only have to make sure that upstream apps do not rely on the system's default. This assumes 1). 3) Not assuming 1), it's possible for python-support to symlink *.py files to /var/lib/python-support and we could ./configure with this python-path as in 2). 4) python-support could be changed to allow a second mode of operations, configurable on a per-package basis, which would symlink *.py into /usr/lib/pythonX.Y/site-packages and byte-compile there as well (option a)) or symlink to byte-compiled files (option b)) under /var/lib/python-support. This compatibility mode could be turned on by default or only for problematic packages. Please tag this bug "wontfix" if you do not think it will ever fix. I intend to use this bug report as a documentation pointer on this problem, but feel free to include this description in some KNOWNBUGS file, or as a step to watch carefully when converting packages to python-support, or when preparing new upstream releases of python packages. Bye, -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-2-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Versions of packages python-support depends on: ii python 2.4.4-1 An interactive high-level object-o python-support recommends no packages. -- no debconf information -- Loïc Minier <[EMAIL PROTECTED]>
--- End Message ---
--- Begin Message ---Source: python-support Source-Version: 0.6.1 We believe that the bug you reported is fixed in the latest version of python-support, which is due to be installed in the Debian FTP archive: python-support_0.6.1.dsc to pool/main/p/python-support/python-support_0.6.1.dsc python-support_0.6.1.tar.gz to pool/main/p/python-support/python-support_0.6.1.tar.gz python-support_0.6.1_all.deb to pool/main/p/python-support/python-support_0.6.1_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josselin Mouette <[EMAIL PROTECTED]> (supplier of updated python-support package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Sat, 24 Feb 2007 13:04:23 +0100 Source: python-support Binary: python-support Architecture: source all Version: 0.6.1 Distribution: experimental Urgency: low Maintainer: Josselin Mouette <[EMAIL PROTECTED]> Changed-By: Josselin Mouette <[EMAIL PROTECTED]> Description: python-support - automated rebuilding support for python modules Closes: 397895 Changes: python-support (0.6.1) experimental; urgency=low . * pysupport-movemodules: + Fix a case where the original installation directory was not removed. + Move modules from /var/lib/python-support as well. This allows to handle packages that hardcode the path to the modules (closes: #397895). * README: + Document the procedure for such packages. + Also document the Python-Depends field. Files: 2379a2969c85c90a0a865eebd9063c90 553 python optional python-support_0.6.1.dsc a7cd6337820708febdf0fa86cb5682bf 27679 python optional python-support_0.6.1.tar.gz 19551b1ec3e999886eb505857842aaec 24866 python optional python-support_0.6.1_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF4Cu+rSla4ddfhTMRAmcoAJ9NS61fWx0T3AY98Gd50gKfwCQgKQCfdIFX 9+1MLYXlYLZZ/tnAgcMEq6g= =Vn5b -----END PGP SIGNATURE-----
--- End Message ---
