Sync calibre 5.3.0+dfsg-1 (universe) from Debian unstable (main)

Bug #1901921 reported by Carlos Pita
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calibre (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Please sync calibre 5.3.0+dfsg-1 (universe) from Debian unstable (main)

Ubuntu 20.04 LTS has shipped a beta version of calibre that is unable
to even start.

Upstream report: https://bugs.launchpad.net/calibre/+bug/1877180

Downstream report: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1898904

There has been a fix for five months now.

Please, either sync to a working version or apply a patch with the fix
described in https://bugs.launchpad.net/calibre/+bug/1877180/comments/6
(although I think the right thing to do is to sync, because this is just
a patch for beta in an LTS).

This is a sync request for focal and maybe also groovy (see comments below).

Changelog entries since current hirsute version 4.99.12+dfsg+really4.23.0-1:

calibre (5.3.0+dfsg-1) unstable; urgency=medium

  * Update patch metadata.
    This helps gbp-pq(1) .
    $ gbp pq import
  * Refresh quilt patches.
    Done by gbp-pq(1) .
    $ gbp pq export
  * New upstream version 5.3.0+dfsg
  * Update Quilt patch

 -- YOKOTA Hiroshi <email address hidden> Fri, 16 Oct 2020 20:03:33 +0900

calibre (5.2.0+dfsg-1) unstable; urgency=medium

  * New upstream version 5.2.0+dfsg

 -- YOKOTA Hiroshi <email address hidden> Wed, 07 Oct 2020 21:10:55 +0900

calibre (5.1.0+dfsg-1) unstable; urgency=medium

  * New upstream version 5.1.0+dfsg

 -- YOKOTA Hiroshi <email address hidden> Fri, 02 Oct 2020 21:14:24 +0900

calibre (5.0.1+dfsg-1) unstable; urgency=medium

  [ Norbert Preining ]
  * initial work on sip5 support (see ##964125)
  * adjust sip deps according to bug report
  * more suggestions concerning sip5
  * test build changelog entry

  [ YOKOTA Hiroshi ]
  * Lintian fix
    get-orig-source target is obsolete.
  * Enable uscan to import source
  * Lintian fix.
    Don't use bulleted list in NEWS entry.
  * Lintian fix.
    All patch files are must in debian/patches/series .
  * Lintian fix.
    Remove trailing white space
  * Lintian fix.
    Add descriptions to quilt patch
  * Lintian fix.
    Each package has different description from other packages.
  * Lintian fix.
    Add upstream bug tracker
  * Lintian fix.
    Theses patches are Debian-only.
    Not needed to forward upstream.
  * Sort dependency lines
  * Lintian fix.
    Remove duplicated lines
  * Lintian fix.
    There is no need to root privileges.
    Don't install default config files.
  * Lintian fix.
    Don't install empty directory
  * Cosmetic fix
  * Use latest version of "poppler-utils" (Closes: #962668)
    Older "pdftohtml" provides surrogate pair characters in UTF-8 string.
    This behavior is not valid for UTF-8 encoding.
    Use latest "pdftohtml" to avoid some error on "python3-lxml".
  * Remove unused target
  * Use trampoline script to Makefile target
  * Use Automatic environment values
  * Refactor parallel build
  * Fix jobserver warning
  * Add comment for trampoline script
  * Remove version mangle
  * Use beta versions as upstream code
  * Update gbp config
    "uscan = True" is not works well
  * New upstream version 4.99.17
  * Remove py3 patches.
    All patches were merged into upstream master branch.
  * Refresh patches
  * Remove unused line
  * Revert SIP5 code.
    Debian doesn't support SIP5 based PyQt5 yet.
  * Reorder to work patches well
  * No need to forward for upstream
  * Remove obsolete document
  * Update document
  * Update changelog
  * Restore version mangle.
    They are still needed because Debian uses own MathJax code.
  * Restore watch file
  * New upstream version 5.0.0+dfsg
  * Drop obsolete patch (Closes: #964125, #970921)
  * Update hardening patch
  * Restore hardening code for SIP
  * New upstream version 5.0.1+dfsg

 -- YOKOTA Hiroshi <email address hidden> Sat, 26 Sep 2020 00:39:18 +0900

Revision history for this message
Carlos Pita (carlosjosepita) wrote :

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.

Revision history for this message
Thomas Ward (teward) wrote :

A note: hirsute should autosync from Debian once the automatic sync/import system is turned on. This doesn't happen necessarily immediately. Bit too late in the cycle to have a 'sync' for Focal and Groovy, those'll need individual patching/SRUs.

Revision history for this message
Carlos Pita (carlosjosepita) wrote :

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.

Revision history for this message
Carlos Pita (carlosjosepita) wrote :

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.

Revision history for this message
Carlos Pita (carlosjosepita) wrote :
Revision history for this message
Thomas Ward (teward) wrote :

I think you've missed my point, which is that it's **extraordinarily rare** we would sync directly from Debian to already-released Ubuntu releases...

Revision history for this message
Carlos Pita (carlosjosepita) wrote :

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: updated
description: updated
Revision history for this message
Carlos Pita (carlosjosepita) wrote :

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.

description: updated
Revision history for this message
Carlos Pita (carlosjosepita) wrote :

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 a few months ago in focal), so maybe it's a recently updated dependency (or an update of calibre itself, but why) that broken the package.

description: updated
description: updated
description: updated
Revision history for this message
Carlos Pita (carlosjosepita) wrote :

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 → Invalid
Revision history for this message
Carlos Pita (carlosjosepita) wrote :

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.launchpad.net/ubuntu/+source/calibre/+bug/1898904/comments/7), Calibre >=4.15 has the required patch. So, instead of waiting for 5.2, can we backport current Groovy version of Calibre to Focal?

So I'm reopening this and letting you close it or follow this suggestion instead.

Changed in calibre (Ubuntu):
status: Invalid → New
Revision history for this message
Balint Reczey (rbalint) wrote :

Calibre is at 5.3.0+dfsg-1 in Hirsute, thus the sync took place.
Please use a different bug for the SRUs.
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

Changed in calibre (Ubuntu):
status: New → 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.