Skip to content

fix: pin pygobject pip package to 3.50.0 #223

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

MarkoSagadin
Copy link

Versions of pygobject from 3.51.0 forward require
libgirepository-2.0-dev as a dependency, but that one is not yet available on the Ubuntu 22.04 (it is on 24.04).

3.50.0 version requires libgirepository-1.0-dev, which is available on the Ubuntu 22.04, however that package was never explicitly installed, so this commit also adds it.

By pinning the pip package and adding new apt package we ensure that Dockerfile.base can be even built.

Closes: #222

Versions of pygobject from 3.51.0 forward require
libgirepository-2.0-dev as a dependency, but that one is not yet
available on the Ubuntu 22.04 (it is on 24.04).

3.50.0 version requires libgirepository-1.0-dev, which is available on
the Ubuntu 22.04, however that package was never explicitly installed,
so this commit also adds it.

By pinning the pip package and adding new apt package we ensure that
Dockerfile.base can be even built.

Closes: zephyrproject-rtos#222
Copy link
Member

@stephanosio stephanosio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By pinning the pip package and adding new apt package we ensure that Dockerfile.base can be even built.

It seems the base Docker image currently builds successfully without this change. Is this expected?

@MarkoSagadin
Copy link
Author

MarkoSagadin commented Apr 23, 2025

Hi, sorry for the late response.

You are right, the base image builds successfully, but I remember that I tried to build it, before opening the linked issue and this PR.

I have built the image locally and checked the version of the installed pygobject package, it is 3.42.1.
So this is the before the breaking change that I witnessed.

Maybe pip decided that this version of the pygoobject is compatible with all other versions and that's why it doesn't try to install more recent one?

Anyway, I guess that this PR (and issue) can be closed, please do so if you see fit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Latest version of PyGObject requires Ubuntu 24.04
2 participants