pango: 1.43.0 -> 1.44.5

[mmahut]

Motivation for this change

pango: 1.43.0 -> 1.44.1

Also fixes #65651.

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Ensured that relevant documentation is up to date
• Fits CONTRIBUTING.md.

Notify maintainers

cc @7c6f434c

[worldofpeace]

Should go to staging.

[jtojnar]

Relevant blog posts:

• https://blogs.gnome.org/mclasen/2019/07/19/pango-updates/
• https://blogs.gnome.org/mclasen/2019/07/27/more-text-rendering-updates/

[jtojnar]

Also note that this release removes support for some bitmap font formats, which some users can still be relying on:

https://gitlab.gnome.org/GNOME/pango/issues/386

[dtzWill]

https://gitlab.gnome.org/GNOME/pango/blob/1.44.1/NEWS <-- maybe bump to this?

FWIW lilypond and inkscape (so far) are failing to build after moving to 1.44.1 -- haven't tried with 1.44.0, so dunno but just heads-up regardless. Looking forward to the bump!

[mmahut]

@GrahamcOfBorg build inkscape lilypond

[mmahut]

@GrahamcOfBorg build lilypond-unstable

[dtzWill]

Phew, 1.44.4 LGTM so far-- builds through inkscape/lilypond locally now \o/.

FWIW: https://gitlab.freedesktop.org/cairo/cairo/issues/370 -- I'm still building but even when that's done may only be able to report if things are dramatically impacted O:). So if someone with sharper eyes or familiarity might wanna check we don't regress font rendering as some users encounter (unless using latest cairo git).

Also, as an experiment I've been rocking freetype w/o cleartype (to see how the default ("Harmony"?) rendering compares) so whatever I end up seeing re:subpixel behavior is likely not representative anyway....

[dtzWill]

@GrahamcOfBorg build python2Packages.pygtk

[mmahut]

@GrahamcOfBorg build python2Packages.pygtk

[worldofpeace]

Tbh, this is something that I'd consider merging after the release...
Other opinions are welcome though.

[mmahut]

@worldofpeace I agree, I don't think we will have this working before anyway.

[worldofpeace]

Right, issues with fonts are already pretty dissatisfying for users, I believe arch is just using cairo master and I don't think we should do this.

[disassembler]

@mmahut @dtzWill netbsd, LFS and archlinux all have similar bugs reported with building pygtk with this pango:

pango.c:8650:55: error: ‘PANGO_TYPE_FONTSET_SIMPLE’ undeclared (first use in this function); did you mean ‘PANGO_TYPE_FONT_FAMILY’?
     pygobject_register_class(d, "PangoFontsetSimple", PANGO_TYPE_FONTSET_SIMPLE, &PyPangoFontsetSimple_Type, Py_BuildValue("(O)", &PyPangoFontset_Type));
                                                       ^~~~~~~~~~~~~~~~~~~~~~~~~
                                                       PANGO_TYPE_FONT_FAMILY

[worldofpeace]

@disassembler I think we can get the security fixes without bumping to 1.44.

[worldofpeace]

Pango re-added the PangoFontsetSimple

• https://gitlab.gnome.org/GNOME/pango/issues/417

So hopefully pygtk can build with that commit now.
(probably need to disable a lot of warnings)