Hi Matthias,
On Fri, 20 Nov 2020, Matthias Klose wrote:
> packaging bug. calibre-bin is rebuilt for 3.9, but you are still calling 3.8.
> You really should use dh_python3 and ${python3:Substvars}.
I am not sure what you are referring to, but we don't call 3.8. We call
/usr/bin/python3
On 11/20/20 3:32 PM, Matthias Klose wrote:
> Control: reassign -1 calibre
> Control: severity -1 serious
>
> On 11/20/20 1:27 PM, Debian Bug Tracking System wrote:
>> Processing commands for cont...@bugs.debian.org:
>>
>>> clone 975284 -1
>> Bug #975284 [ca
Control: reassign -1 calibre
Control: severity -1 serious
On 11/20/20 1:27 PM, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
>
>> clone 975284 -1
> Bug #975284 [calibre] calibre: crashes on start
> Bug 975284 cloned as bug 975320
>
On Fri, 20 Nov 2020 21:22:00 +0900, Norbert Preining wrote:
> > ImportError: /usr/lib/calibre/calibre/plugins/progress_indicator.so:
> > undefined symbol: _Py_FatalErrorFunc
JFTR, this looks similar for pure commandline usage:
% calibre catalog
Traceback (most recent call last):
File
clone 975284 -1
reassign -1 python3
retitle -1 breaks unrelated packages
thanks
Hi
On Fri, 20 Nov 2020, Hor Jiun Shyong wrote:
> After upgrading to version 5.5.0+dfsg-1, calibre crashes on start.
ACtually, this is independent of the upgrade, but an effect of some
python3 upgrade, I guess the
Subject: calibre: crashes on start
Package: calibre
Version: 5.5.0+dfsg-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
After upgrading to version 5.5.0+dfsg-1, calibre crashes on start.
Error logs:
$calibre
Traceback (most recent
6 matches
Mail list logo
