Exaile 0.2.14+debian-1 don't launch : Feedparser problem

Bug #364279 reported by Max Ruman
4
Affects Status Importance Assigned to Milestone
Exaile
Invalid
Undecided
alyarmak
exaile (Debian)
Fix Released
Unknown

Bug Description

I've just installed Exaile 0.2.14+debian-1 from Debian official repositories (testing/unstable), and when I start it :

/home/rmx/.themes/tropical/gtk-2.0/gtkrc:89: Murrine configuration option "highlight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
/home/rmx/.themes/tropical/gtk-2.0/gtkrc:90: Murrine configuration option "lightborder_ratio" will be deprecated in future releases. Please use "lightborder_shade" instead.
/home/rmx/.themes/tropical/gtk-2.0/gtkrc:105: Murrine configuration option "style" is not supported and will be ignored.
/home/rmx/.themes/tropical/gtk-2.0/gtkrc:157: Murrine configuration option "highlight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
Traceback (most recent call last):
  File "/usr/lib/exaile/exaile.py", line 94, in <module>
    from xl.gui import main as exailemain
  File "/usr/lib/exaile/xl/gui/main.py", line 29, in <module>
    from xl.panels import collection, radio, playlists, files, device
  File "/usr/lib/exaile/xl/panels/radio.py", line 18, in <module>
    from lib import feedparser
ImportError: cannot import name feedparser
zsh: exit 1 exaile

And # dpkg-reconfigure exaile gives me :

WARNING: I/O error while trying to byte-compile /usr/lib/exaile/lib/feedparser.py (2): No such file or directory

Revision history for this message
Johannes Sasongko (sjohannes) wrote :

This has something to do with Debian's patch for 0.2.14+debian-1. The corresponding change is "Do not ship feedparser.py anymore, depends on the standalone package." [1], i.e. it removes lib/feedparser.py and instead links the file provided by python-feedparser into lib.

[1] http://packages.debian.org/changelogs/pool/main/e/exaile/exaile_0.2.14+debian-1/changelog#versionversion0.2.14_debian-1

I'm not familiar enough with Debian's packaging system to know whether it's a bug on their end or something that you did wrong; I suggest filing a report at the Debian BTS.

Changed in exaile:
status: New → Invalid
alyarmak (alyarmak)
Changed in exaile:
assignee: nobody → alyarmak
Changed in exaile (Debian):
status: Unknown → New
Changed in exaile (Debian):
status: New → Fix Committed
Changed in exaile (Debian):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.