Your message dated Tue, 9 Sep 2014 18:27:35 +0200
with message-id 
<CAJGOOk_=ufnhxgzh-j8gbr6tzlxlri-avlaxn_0dwa5kocc...@mail.gmail.com>
and subject line Re: python3-pyinotify: incompatible with python3.3 in 
experimental
has caused the Debian Bug report #704593,
regarding python3-pyinotify: incompatible with python3.3 in experimental
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.)


-- 
704593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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

Attachment: shatag_0.4-3.log.gz
Description: GNU Zip compressed data


--- End Message ---
--- Begin Message ---
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.

--- End Message ---

Reply via email to