Your message dated Thu, 10 Nov 2011 02:09:17 +0000
with message-id <4ebb324d.5040...@postgrad.manchester.ac.uk>
and subject line re: libvirt-glib: FTBFS: /bin/sh: python2.5: not found
has caused the Debian Bug report #588596,
regarding libvirt-glib: FTBFS: /bin/sh: python2.5: not found
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 ow...@bugs.debian.org
immediately.)
--
588596: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvirt-glib
Version: 0~0.git22fac-1
Severity: serious
Justification: FTBFS
Hello,
Your package fails to build from source in a clean sid chroot. The
relevant part of the build log:
[…]
| set -e; for buildver in 2.5 2.6; do \
| cd /tmp/buildd/libvirt-glib-0~0.git22fac && cd . && python$buildver
/dev/null build --build-base="/tmp/buildd/libvirt-glib-0~0.git22fac/./build"; \
| done
| /bin/sh: python2.5: not found
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
Jakub Wilk
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
version: 0.0.1~1.git55696-1
This appears to be fixed in the current version.
--- End Message ---
