Bug#704593: python3-pyinotify: incompatible with python3.3 in experimental
Closing this bug as it is not reproducible anymore. On 2 September 2014 01:23, Mikhail Gusarov dotted...@debian.org wrote: Hi. Is there any way to reproduce this issue? I'll close this bug in a week if there is not, to ensure pyinotify does not fall off testing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704593: python3-pyinotify: incompatible with python3.3 in experimental
Hi. Is there any way to reproduce this issue? I'll close this bug in a week if there is not, to ensure pyinotify does not fall off testing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704593: python3-pyinotify: incompatible with python3.3 in experimental
Control: tags -1 + moreinfo
Hi Andreas,
On 2013-04-03 12:17:13, Andreas Beckmann wrote:
Package: python3-pyinotify
Version: 0.9.3-1.1
Severity: serious
Tags: experimental
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + shatag
Hi,
during a test with piuparts I noticed your package failed to install.
From the attached log (scroll to the bottom...):
Setting up libpython3.3-minimal:amd64 (3.3.1~rc1-1) ...
Setting up mime-support (3.53~experimental2) ...
update-alternatives: using /usr/bin/see to provide /usr/bin/view (view) in
auto mode
Setting up libpython3.3-stdlib:amd64 (3.3.1~rc1-1) ...
Setting up python3.3-minimal (3.3.1~rc1-1) ...
Setting up python3.3 (3.3.1~rc1-1) ...
Setting up python3-minimal (3.3.0-3) ...
Setting up python3 (3.3.0-3) ...
Setting up python3-pyinotify (0.9.3-1.1) ...
Traceback (most recent call last):
File /usr/bin/py3compile, line 292, in module
main()
File /usr/bin/py3compile, line 272, in main
options.force, options.optimize, e_patterns)
File /usr/bin/py3compile, line 158, in compile
cfn = interpreter.cache_file(fn, version)
File /usr/share/python3/debpython/interpreter.py, line 212, in
cache_file
(fname[:-3], self.magic_tag(version), last_char))
File /usr/share/python3/debpython/interpreter.py, line 246, in magic_tag
return self._execute('import imp; print(imp.get_tag())', version)
File /usr/share/python3/debpython/interpreter.py, line 359, in _execute
raise Exception('{} failed with status code {}'.format(command,
output['returncode']))
Exception: python3.2 -c 'import imp; print(imp.get_tag())' failed with
status code 134
dpkg: error processing python3-pyinotify (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up python3.2-minimal (3.2.3-7) ...
Setting up python3.2 (3.2.3-7) ...
Errors were encountered while processing:
python3-pyinotify
I fail to reproduce the issue with python3-pyinotify 0.9.3-2. I get the
same sequence at the end but without the failure:
| Setting up libssl1.0.0:amd64 (1.0.1e-3) ...
| debconf: unable to initialize frontend: Dialog
| debconf: (No usable dialog-like program is installed, so the dialog based
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line
76.)
| debconf: falling back to frontend: Readline
| Setting up libmagic1:amd64 (1:5.14-2) ...
| Setting up libexpat1:amd64 (2.1.0-3) ...
| Setting up libffi6:amd64 (3.0.13-4) ...
| Setting up libpython3.3-minimal (3.3.2-2) ...
| Setting up libpython3.3-stdlib (3.3.2-2) ...
| Setting up file (1:5.14-2) ...
| Setting up python3.3-minimal (3.3.2-2) ...
| Setting up python3.3 (3.3.2-2) ...
| Setting up python3-minimal (3.3.0-3) ...
| Setting up python3 (3.3.0-3) ...
| running python rtupdate hooks for python3.3...
| running python post-rtupdate hooks for python3.3...
| Setting up python3-pyinotify (0.9.3-2) ...
| Setting up python3.2-minimal (3.2.4-1) ...
| Setting up python3.2 (3.2.4-1) ...
| Processing triggers for libc-bin ...
| ldconfig deferred processing now taking place
So either this is fixed somehow or it's another case of Python related
maintainer script breakage. Are you still able to reproduce this issue?
Nevertheless it'd be interesting to see why python3.2 aborted.
Regards
--
Sebastian Ramacher
signature.asc
Description: Digital signature
Bug#704593: python3-pyinotify: incompatible with python3.3 in experimental
Control: tag -1 - moreinfo On 2013-05-24 20:27, Sebastian Ramacher wrote: On 2013-04-03 12:17:13, Andreas Beckmann wrote: Exception: python3.2 -c 'import imp; print(imp.get_tag())' failed with status code 134 whatever that actually executed ... I fail to reproduce the issue with python3-pyinotify 0.9.3-2. I get the same sequence at the end but without the failure: ... So either this is fixed somehow or it's another case of Python related maintainer script breakage. Are you still able to reproduce this issue? No. Just tried installing python3-pyinotify (0.9.3-2) with piuparts in both sid end experimental ... and everything went smooth. Nevertheless it'd be interesting to see why python3.2 aborted. and it only happened in experimental ... Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704593: python3-pyinotify: incompatible with python3.3 in experimental
* Andreas Beckmann a...@debian.org, 2013-04-03, 12:17:
Traceback (most recent call last):
File /usr/bin/py3compile, line 292, in module
main()
File /usr/bin/py3compile, line 272, in main
options.force, options.optimize, e_patterns)
File /usr/bin/py3compile, line 158, in compile
cfn = interpreter.cache_file(fn, version)
File /usr/share/python3/debpython/interpreter.py, line 212, in cache_file
(fname[:-3], self.magic_tag(version), last_char))
File /usr/share/python3/debpython/interpreter.py, line 246, in magic_tag
return self._execute('import imp; print(imp.get_tag())', version)
File /usr/share/python3/debpython/interpreter.py, line 359, in _execute
raise Exception('{} failed with status code {}'.format(command,
output['returncode']))
Exception: python3.2 -c 'import imp; print(imp.get_tag())' failed with status
code 134
dpkg: error processing python3-pyinotify (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up python3.2-minimal (3.2.3-7) ...
Setting up python3.2 (3.2.3-7) ...
Errors were encountered while processing:
python3-pyinotify
python3.2 seems to be used before it gets configured, that may indicate
a bug in another python package (e.g. incorrect dependencies).
It was my theory as well that the problem is that py3compile calls
/usr/bin/python3.2 when python3.2(-minimal) in the middle of the
upgrade. But on a second thought:
- Both python3.2-minimal and python3.2 seem to have their dependencies
satisfied, as they could be configured immediately after failure.
- I can't see anything vital in their maintainer scripts that would
explain such failure.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704593: python3-pyinotify: incompatible with python3.3 in experimental
Package: python3-pyinotify
Version: 0.9.3-1.1
Severity: serious
Tags: experimental
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + shatag
Hi,
during a test with piuparts I noticed your package failed to install.
From the attached log (scroll to the bottom...):
Setting up libpython3.3-minimal:amd64 (3.3.1~rc1-1) ...
Setting up mime-support (3.53~experimental2) ...
update-alternatives: using /usr/bin/see to provide /usr/bin/view (view) in
auto mode
Setting up libpython3.3-stdlib:amd64 (3.3.1~rc1-1) ...
Setting up python3.3-minimal (3.3.1~rc1-1) ...
Setting up python3.3 (3.3.1~rc1-1) ...
Setting up python3-minimal (3.3.0-3) ...
Setting up python3 (3.3.0-3) ...
Setting up python3-pyinotify (0.9.3-1.1) ...
Traceback (most recent call last):
File /usr/bin/py3compile, line 292, in module
main()
File /usr/bin/py3compile, line 272, in main
options.force, options.optimize, e_patterns)
File /usr/bin/py3compile, line 158, in compile
cfn = interpreter.cache_file(fn, version)
File /usr/share/python3/debpython/interpreter.py, line 212, in cache_file
(fname[:-3], self.magic_tag(version), last_char))
File /usr/share/python3/debpython/interpreter.py, line 246, in magic_tag
return self._execute('import imp; print(imp.get_tag())', version)
File /usr/share/python3/debpython/interpreter.py, line 359, in _execute
raise Exception('{} failed with status code {}'.format(command,
output['returncode']))
Exception: python3.2 -c 'import imp; print(imp.get_tag())' failed with status
code 134
dpkg: error processing python3-pyinotify (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up python3.2-minimal (3.2.3-7) ...
Setting up python3.2 (3.2.3-7) ...
Errors were encountered while processing:
python3-pyinotify
python3.2 seems to be used before it gets configured, that may indicate a bug
in another python package (e.g. incorrect dependencies).
cheers,
Andreas
shatag_0.4-3.log.gz
Description: GNU Zip compressed data
