My only guess is that /usr/bin/bst somehow uses the version of bst I have installed with pip.
That's standard Python behaviour:
>>> import sys >>> sys.path ['', '/usr/lib64/python37.zip', '/usr/lib64/python3.7', '/usr/lib64/python3.7/lib-dynload', '/home/mathieu/.local/lib/python3.7/site-packages', '/usr/lib64/python3.7/site-packages', '/usr/lib/python3.7/site-packages']
Python searches for modules to import in those directories in this order, so the one in your homedir gets imported before the system one.
So if you install Buildstream both from the package and with
pip install --user, you're always using the one in your homedir.
You probably only want to use one, not both.
With 1.4.0, GNOME Software would hang completely when trying to update a Flatpak app, showing this in the terminal:
09:21:17:0369 GLib-GObject specified class size for type 'GsFlatpakTransaction' is smaller than the parent type's 'FlatpakTransaction' class size
This update fixes that.
This bumps soname, should this really be pushed as a stable update?
hplip was rebuilt against this, and made it to stable independently, so it's now broken. When a soname bumping update like this really has to be pushed to stable, all the dependent packages should be bundled in the same update so they all go to stable at the same time.