[Bug 1951069] Re: [MIR] raqm

[Dave Jones]

Thanks for the swift review!

- check if the autopkgtests can be enhanced

I could add an autopkgtest to re-run the full test suite, but given the
full test suite is already executed during the build itself, I'm not
sure how much extra safety that buys us?

- check why 0.7.1 and 0.7.2 ara available (from Nov 2020 for the former)
without any update on debian/ubuntu. As the package hasn’t changed for
multiple releases. I think those fixes are not distro-patched either.

Looking at the upstream history it would appear that (so far) they've
only dealt with bumps to the minor version (0.3, 0.5, 0.6, 0.7) and not
to sub-minor releases (0.7.1). To see whether that results in missing
anything important, I dug into the two releases that are currently not
packaged:

Looking at the changes from 0.7.0 to 0.7.1 (https://github.com/HOST-
Oman/libraqm/compare/v0.7.0...v0.7.1) it's entirely housekeeping
(changing library requirements to fit their CI requirements), adding
bits for other platform builds (macOS, Fedora), and removing legacy
requirements (python 2; which was already patched upstream). In other
words, I can understand why upstream didn't see a pressing need to
package it yet (it doesn't fix any bugs, nor add any new functionality,
and given the existence of the py3 patch, it doesn't remove any awkward
build-deps either, though arguably it would remove the single patch
against the orig-tar).

0.7.1 to 0.7.2 is rather more interesting (https://github.com/HOST-
Oman/libraqm/compare/v0.7.1...v0.7.2), but also considerably more recent
having only been released at the end of  September this year. It does
fix several bugs, but the majority of the changes are to do with the
addition of the meson build system (and deprecation of autotools for
future releases). The (relevant) bugs fixed are a failure with newer
harfbuzz libraries (https://github.com/HOST-Oman/libraqm/issues/135),
beyond the harfbuzz version currently in Debian/Ubuntu, leaving just the
spacing of color emojis (https://github.com/HOST-
Oman/libraqm/issues/123).

** Bug watch added: github.com/HOST-Oman/libraqm/issues #135
   https://github.com/HOST-Oman/libraqm/issues/135

** Bug watch added: github.com/HOST-Oman/libraqm/issues #123
   https://github.com/HOST-Oman/libraqm/issues/123

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to raqm in Ubuntu.
https://bugs.launchpad.net/bugs/1951069

Title:
  [MIR] raqm

Status in raqm package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
  The package is already in universe.

  [Rationale]
  The package is a new dependency of pillow, which is already in main.

  [Security]
  There are currently no CVEs mentioning raqm, and the project is actively maintained upstream.

  [Quality assurance]
  There are no currently outstanding bugs in Launchpad for the package, there is a good test suite within the project itself (which is run during the build), and the package includes a build test for autopkgtest.

  [UI standards]
  Only applicable insofar as raqm adds advanced text layout capabilities to the Pillow library.

  [Dependencies]
  The build+installation dependencies of the library are:
  * freetype -- already in main
  * fribidi -- already in main
  * harfbuzz -- already in main

  [Standards compliance]
  The package installs its libraries in the typical location (e.g. /usr/lib/x86_64-linux-gnu/ on a PC).

  [Maintenance]
  The package will be maintained by the Ubuntu Foundations team.

  [Background information]
  The Pillow package cannot currently migrate due to component mismatch errors as raqm is a new dependency added in Pillow 8.2.0 (or more specifically Pillow 8.2.0 "link[ed] against the system version of libraqm at build time rather than at runtime by default").

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/raqm/+bug/1951069/+subscriptions