Package: meld Version: 1.1.5.1-2 Severity: normal
Is there a reason that the shebang line for /usr/bin/meld uses /bin/env python, rather than /usr/bin/python? Using /bin/env causes the program to fail if the user has another version of python somewhere earlier on their path, if that version of python doesn't happen to have pygtk built. Since you're already depending on a local python being installed, presumably it should simply use /usr/bin/python? Regards, Tim -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages meld depends on: ii python 2.5.2-3 An interactive high-level object-o ii python-glade2 2.12.1-6 GTK+ bindings: Glade support ii python-gnome2 2.22.0-1 Python bindings for the GNOME desk ii python-gtk2 2.12.1-6 Python bindings for the GTK+ widge ii python-support 0.8.4lenny1 automated rebuilding support for P Versions of packages meld recommends: ii python-gnome2-desktop 2.22.0-2 Python bindings for the GNOME desk ii yelp 2.22.1-8+b1 Help browser for GNOME 2 meld suggests no packages. -- no debconf information -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
