Skip to content

Fix the lxml build in the flatpak, and automate maintenance a little further

I've started looking into fixing the build error in the flatpak job; it fails in python's lxml.

  • The build uses lxml 4.9.1 from the resolved python3-requirements.json
  • I want to try the latest lxml, 5.3.0

Per RELEASING.md, refreshing python3-requirements.json is a bit involved and requires some manual work, plus having flatpak-builder-tools somewhere.

Here's my current plan, but of course @jrb should tell me what would be easiest for him as maintainer 😄

  1. Put a checkout of flatpak-builder-tools somewhere in the CI image. It already uses /usr/local/python for the build-time pip requirements; we can use /usr/local/flatpak-builder-tools as a starting point just to have the scripts there.
  2. Write a ci/update-python-requirements script that will automatically do the steps from RELEASING.md. If it needs to modify the output JSON after running flatpak-pip-generator to account for development packages, so be it. Let's figure it out once and avoid manual work.
  3. (handwaves) actually get the updated lxml to build and see if it works. I think it's only used in jpzconvertor.py - is this correct?