Public bug reported:
Please sync calibre 5.3.0+dfsg-1 (universe) from Debian unstable (main)
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971947
Ubuntu 20.04 LTS has shipped a beta version of calibre that is unable
to even start.
There has been a fix for five months now.
Please, eithe
I've reported this with the requestsync tool but:
> Changelog entries since current hirsute version
4.99.12+dfsg+really4.23.0-1:
seems wrong to me since my version is focal, not groovy nor hirsute.
--
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is sub
I know @teward, and this is probably already fixed in groovy (I've not
tested that), but the request is for focal despite what the description
says (see comment #1 above). It's specially important for focal since
the package is non-functional as it is and focal is an LTS relase.
--
You received t
Well, groovy is shipping
4.99.12+dfsg+really4.23.0-1
instead of
4.99.4+dfsg+really4.12.0-1build1:
which is in focal.
Both are beta releases, so probably both worth syncing.
--
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to calib
See also https://askubuntu.com/questions/1285431/calibre-no-longer-
working
--
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to calibre in Ubuntu.
https://bugs.launchpad.net/bugs/1901921
Title:
Sync calibre 5.3.0+dfsg-1 (universe) from De
Is it because that would imply syncing dependencies also? I've not
checked if that's the case. FWIW the workaround in comment
https://bugs.launchpad.net/calibre/+bug/1877180/comments/6 works for me
as far as I can see.
--
You received this bug notification because you are a member of Edubuntu
Bug
I'm surely requesting an exception here since the package shipped in
focal doesn't even start, I believe you cannot go worse than that by
syncing.
** Description changed:
Please sync calibre 5.3.0+dfsg-1 (universe) from Debian unstable (main)
- See https://bugs.debian.org/cgi-bin/bugreport.c
When this started to happen? I would be surprised if it was an update to
focal (why?), but I have the feeling this was working at the beginning.
--
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to calibre in Ubuntu.
https://bugs.launchpad.ne
** Description changed:
Please sync calibre 5.3.0+dfsg-1 (universe) from Debian unstable (main)
- See https://bugs.launchpad.net/calibre/+bug/1877180
+ See https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1898904
Ubuntu 20.04 LTS has shipped a beta version of calibre that is unable
I had confused the upstream tracker with the Ubuntu tracker for Calibre,
since both live in Launchpad, but now that I've seen the downstream
report at https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1898904
it seems like if this started happening recently (I vaguely remember
this was working
Maybe a python upgrade to 3.8.5 at some point since the release of
focal?
--
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to calibre in Ubuntu.
https://bugs.launchpad.net/bugs/1898904
Title:
Calibre crashes at startup with AttributeError
Ok, I'm marking this as invalid after having read this very detailed
description of the situation:
https://forum.snapcraft.io/t/package-calibre-epub-books-reader/20436/11
Besides this particular comment all the thread is worth reading.
** Changed in: calibre (Ubuntu)
Status: New => Invali
Sorry for the noise, but now I'm reading
https://lists.ubuntu.com/archives/ubuntu-devel/2020-October/041237.html
and there was a suggestion there to sync but from Groovy:
> I checked Calibre in Groovy (version 4.99.12+dfsg+really4.23.0-1) and
it works fine. As per bug report #1898904
(https://bugs
Here https://lists.ubuntu.com/archives/ubuntu-
devel/2020-October/041237.html is a suggestion to sync from Groovy to
Focal in order to fix the issue:
> I checked Calibre in Groovy (version 4.99.12+dfsg+really4.23.0-1) and
it works fine. As per bug report #1898904
(https://bugs.launchpad.net/ubuntu
This worked for me, thanks! Anyway, I would like to point out that this
is a problem upstream and it would be nice to port the fix to Debian. I
have emailed the maintainer a couple of times because of this issue but
never got an answer. It would safe to consider upstream to be
unmaintained at this
15 matches
Mail list logo
