Bug#868379: Processed (with 4 errors): python-dateutil: makes calibre fail to start
Hi, On Sun, Jul 16, 2017 at 11:22:47AM +0200, Manolo Díaz wrote: > On Sunday, 16 Jul 2017 at 09:05 UTC > Guido Günther wrote: > > > Hi, > > control: affects -1 calibre > > [...] > > > Starts here without problems. Does > > > > python -c "from six.moves import _thread" > > > > work for you? If it does not work your python-six is broken. Maybe you > > have a local version of six lying around? > > Cheers, > > -- Guido > > Hi, > > python -c "from six.moves import _thread" does apparently nothing and > exits with 0. Is this expected? > Yept. That's how it should be. > The version of python-six on my system is 1.10.0-4 (current testing) > and if it was broken I think calibre wouldn't start with only > downgrading python-dateutil. It might because the old python-dateutil version might not have used it. Can you do a strace -f -s2048 /usr/bin/calibre and attach this to the bugreport please. Cheers, -- Guido
Bug#868379: Processed (with 4 errors): python-dateutil: makes calibre fail to start
On Sunday, 16 Jul 2017 at 09:05 UTC Guido Günther wrote: > Hi, > control: affects -1 calibre [...] > Starts here without problems. Does > > python -c "from six.moves import _thread" > > work for you? If it does not work your python-six is broken. Maybe you > have a local version of six lying around? > Cheers, > -- Guido Hi, python -c "from six.moves import _thread" does apparently nothing and exits with 0. Is this expected? The version of python-six on my system is 1.10.0-4 (current testing) and if it was broken I think calibre wouldn't start with only downgrading python-dateutil. -- Manolo Díaz
Bug#868379: Processed (with 4 errors): python-dateutil: makes calibre fail to start
Hi, control: affects -1 calibre Hi, On Sun, Jul 16, 2017 at 08:42:05AM +, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > > reassign 868379 python-dateutil 2.6.0-1 > Bug #868379 [calibre] calibre: Fails to start with "ImportError: cannot > import name _thread" > Bug reassigned from package 'calibre' to 'python-dateutil'. > No longer marked as found in versions calibre/2.75.1+dfsg-1 and > calibre/3.1.1+dfsg-1. > Ignoring request to alter fixed versions of bug #868379 to the same values > previously set > Bug #868379 [python-dateutil] calibre: Fails to start with "ImportError: > cannot import name _thread" > Marked as found in versions python-dateutil/2.6.0-1. > > retitle 868379 python-dateutil: makes calibre fail to start > Bug #868379 [python-dateutil] calibre: Fails to start with "ImportError: > cannot import name _thread" > Changed Bug title to 'python-dateutil: makes calibre fail to start' from > 'calibre: Fails to start with "ImportError: cannot import name _thread"'. > > Dear Maintainer, > Unknown command or malformed arguments to command. > > python-dateutil 2.6.0-1 makes calibre fail to start. Downgrading it to > Unknown command or malformed arguments to command. > > version 2.5.3-2 fixes this problem. > Unknown command or malformed arguments to command. > > Best Regards, > Unknown command or malformed arguments to command. > > -- > Stopping processing here. Starts here without problems. Does python -c "from six.moves import _thread" work for you? If it does not work your python-six is broken. Maybe you have a local version of six lying around? Cheers, -- Guido
