Package: moosic
Version: 1.5.5-1
Severity: important

On my system, moosic now dies on launch, with the following output:

================
Traceback (most recent call last):
  File "/usr/bin/moosic", line 6, in <module>
    main(sys.argv)
File "/usr/lib/python2.6/dist-packages/moosic/client/cli/main.py", line 243, in main
    moosic.no_op()
  File "/usr/lib/python2.6/xmlrpclib.py", line 1199, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib/python2.6/xmlrpclib.py", line 1489, in __request
    verbose=self.__verbose
  File "/usr/lib/python2.6/xmlrpclib.py", line 1237, in request
    errcode, errmsg, headers = h.getreply()
AttributeError: HTTPConnection instance has no attribute 'getreply'
================

That error appears to be the result of a change which arose in Python
2.7. However, since moosic's shebang is "#!/usr/bin/python", and
python-minimal currently installs that as a symlink to 'python2.6', and
the Python libraries listed in the traceback are from python2.6, moosic
is apparently being run with Python 2.6; therefore this error should not
be appearing.

I have now seen this behavior on two different systems, both of which
track testing.

I first saw this error in moosicd, on a system where Python 2.7 was not
installed. Installing the python2.7 package made the error go away for
moosicd, but it still occurs for moosic itself.

If I explicitly launch moosic with python2.7, rather than relying on
the shebang, it runs fine.

This is very probably a bug in one or more of the Python packages, such
that the correct versions of the Python libraries are not always being
used. However, since I have no idea which package(s) are at fault, and
since the problem could be "fixed" by adding a dependency on python2.7
and changing the shebang line, I am reporting it here.

This problem could be worked around at the user end if the
'/usr/bin/python' symlink were handled by the alternatives system.
However, since it is instead installed explicitly by python-minimal,
that is not an advisable solution.

If there is anything I can do to help track down and resolve the
problem, please do not hesitate to let me know. I use moosic daily, and
having to jump through hoops to get it to be usable is exceedingly
inconvenient.


-- System Information:
Debian Release: wheezy/sid
  APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'oldstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages moosic depends on:
ii  python                        2.6.7-3    interactive high-level object-orie
ii  python2.6                     2.6.7-3    An interactive high-level object-o
ii  python2.7                     2.7.2-3    An interactive high-level object-o

Versions of packages moosic recommends:
ii  mpg321                        0.2.13-3   Simple and lightweight command lin

Versions of packages moosic suggests:
ii  mikmod                      3.2.1-2      Portable tracked music player
ii  sox                         14.3.2-1     Swiss army knife of sound processi
ii  timidity                    2.13.2-39+b1 Software sound renderer (MIDI sequ
ii  vorbis-tools                1.4.0-1      several Ogg Vorbis tools

-- no debconf information



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to