Your message dated Tue, 31 May 2011 06:14:56 +0100
with message-id <1306818896.4277.126.camel@localhost>
and subject line Re: python2.5: commands.getstatusoutput fails in i386 chroot
has caused the Debian Bug report #524985,
regarding python2.5: commands.getstatusoutput fails in i386 chroot
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.)
--
524985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python2.5
Version: 2.5.4-1
Severity: important
Hello,
We discovered that my builds of xorg-server for i386 had strange build
strings (see "Build Operating System: ..." in /var/log/Xorg.0.log if
you have xserver-xorg-core 1.6.1 installed).
The reason is that lsb_release -i -s fails in my i386 chroot:
morris:~# lsb_release -i -s
Traceback (most recent call last):
File "/usr/bin/lsb_release", line 96, in <module>
main()
File "/usr/bin/lsb_release", line 60, in main
distinfo = lsb_release.get_distro_information()
File "/usr/lib/pymodules/python2.5/lsb_release.py", line 250, in
get_distro_information
distinfo = guess_debian_release()
File "/usr/lib/pymodules/python2.5/lsb_release.py", line 209, in
guess_debian_release
rinfo = guess_release_from_apt()
File "/usr/lib/pymodules/python2.5/lsb_release.py", line 151, in
guess_release_from_apt
releases = parse_apt_policy()
File "/usr/lib/pymodules/python2.5/lsb_release.py", line 135, in
parse_apt_policy
policy = commands.getoutput('apt-cache policy 2>/dev/null')
File "/usr/lib/python2.5/commands.py", line 44, in getoutput
return getstatusoutput(cmd)[1]
File "/usr/lib/python2.5/commands.py", line 54, in getstatusoutput
text = pipe.read()
IOError: [Errno 9] Bad file descriptor
close failed: [Errno 9] Bad file descriptor
morris:~# Package files:
100 /var/lib/dpkg/status
release a=now
500 http://ftp.debian.org sid/main Packages
release o=Debian,a=unstable,l=Debian,c=main
origin ftp.debian.org
Pinned packages:
The machine is a amd64. lsb_release works fine in a similar amd64 chroot.
I narrowed down the problem using the following python program:
#!/usr/bin/python
import commands
commands.getstatusoutput('echo foobar')
It works outside of chroot on amd64 and i386, and in the amd64 chroot:
But it fails in the i386 chroot:
morris:~# ~bgoglin/test.py
foobar
Traceback (most recent call last):
File "/home/bgoglin/test.py", line 3, in <module>
commands.getstatusoutput('echo foobar')
File "/usr/lib/python2.5/commands.py", line 54, in getstatusoutput
text = pipe.read()
IOError: [Errno 9] Bad file descriptor
close failed: [Errno 9] Bad file descriptor
Brice
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-rc2=topinambour (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash
Versions of packages python2.5 depends on:
ii libbz2-1.0 1.0.5-1 high-quality block-sorting file co
ii libc6 2.9-4 GNU C Library: Shared libraries
ii libdb4.5 4.5.20-13 Berkeley v4.5 Database Libraries [
ii libncursesw5 5.7+20090404-1 shared libraries for terminal hand
ii libreadline5 5.2-4 GNU readline and history libraries
ii libsqlite3-0 3.6.12-1 SQLite 3 shared library
ii libssl0.9.8 0.9.8g-16 SSL shared libraries
ii mime-support 3.44-1 MIME files 'mime.types' & 'mailcap
ii python2.5-minimal 2.5.4-1 A minimal subset of the Python lan
python2.5 recommends no packages.
Versions of packages python2.5 suggests:
pn python-profiler <none> (no description available)
pn python2.5-doc <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.6.26-14
I believe this is a duplicate of #521863, which was fixed in the above
version.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
