Your message dated Wed, 20 Apr 2011 12:38:50 +0200
with message-id <[email protected]>
and subject line Re: Bug#594691: Reopening ticket
has caused the Debian Bug report #594691,
regarding fails to install (missing profiler.py file for python2.7)
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.)
--
594691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594691
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-profiler
Version: 2.6.6-1
Severity: important
| Setting up python-profiler (2.6.6-1) ...
| Traceback (most recent call last):
| File "py_compile.py", line 170, in <module>
| sys.exit(main())
| File "py_compile.py", line 162, in main
| compile(filename, doraise=True)
| File "py_compile.py", line 106, in compile
| with open(file, 'U') as f:
| IOError: [Errno 2] No such file or directory: 'profile.py'
| dpkg: error processing python-profiler (--configure):
| subprocess installed post-installation script returned error exit status 1
| Setting up python2.6-doc (2.6.6-2) ...
| Setting up python2.6-examples (2.6.6-2) ...
| Setting up schroot-common (1.4.10-2) ...
| Setting up schroot (1.4.10-2) ...
| Setting up python2.6-dbg (2.6.6-2) ...
| Processing triggers for menu ...
| Errors were encountered while processing:
| python-profiler
| E: Sub-process /usr/bin/dpkg returned an error code (1)
| A package failed to install. Trying to recover:
| Setting up python-profiler (2.6.6-1) ...
| Traceback (most recent call last):
| File "py_compile.py", line 170, in <module>
| sys.exit(main())
| File "py_compile.py", line 162, in main
| compile(filename, doraise=True)
| File "py_compile.py", line 106, in compile
| with open(file, 'U') as f:
| IOError: [Errno 2] No such file or directory: 'profile.py'
| dpkg: error processing python-profiler (--configure):
| subprocess installed post-installation script returned error exit status 1
| Errors were encountered while processing:
| python-profiler
| $ find /usr/lib/ -maxdepth 2 -name profile.py
| /usr/lib/python2.6/profile.py
| /usr/lib/python2.5/profile.py
note that I have python2.7 installed, but python-prifiler package doesn't
provide this file for Python 2.7 so postinst has to check if the file exist
first
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python-profiler depends on:
ii python 2.6.5-13 interactive high-level object-orie
python-profiler recommends no packages.
Versions of packages python-profiler suggests:
ii python-doc 2.6.5-13 documentation for the high-level o
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.7.1-2
On 04/20/2011 02:53 AM, Norbert Preining wrote:
reopen 594691
found 594691 2.7.1-1
thanks
This bug is still present, and now python2.7 is in unstable:
Setting up python-profiler (2.7.1-1) ...
Traceback (most recent call last):
File "py_compile.py", line 184, in<module>
main()
File "py_compile.py", line 176, in main
compile(filename, doraise=True)
File "py_compile.py", line 115, in compile
f = open(file, 'U')
IOError: [Errno 2] No such file or directory: 'profile.py'
dpkg: error processing python-profiler (--configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
python-profiler
E: Sub-process /usr/bin/dpkg returned an error code (1)
or remove python2.5-minimal for now.
--- End Message ---
