Bug#1022286: gnome-shell-extension-manager: FTBFS: ModuleNotFoundError: No module named 'gi'

Heather Ellsworth heather.ellsworth at canonical.com
Mon Oct 24 20:48:50 BST 2022


Ah yes you are right, I have moved the dependency to the control.in file 
and regenerated the control file. The changes have been pushed to the 
debian/master branch and I'll work with Jeremy to re-upload :)

Cheers,
Heather

On 10/23/22 11:04, Simon McVittie wrote:
> Control: reassign -1 blueprint-compiler 0.4.0-3
> Control: affects -1 + src:gnome-shell-extension-manager
> 
> On Sun, 23 Oct 2022 at 14:38:05 +0200, Lucas Nussbaum wrote:
>>> Program blueprint-compiler found: YES (/usr/bin/blueprint-compiler)
> ...
>>> Traceback (most recent call last):
>>>    File "/usr/bin/blueprint-compiler", line 37, in <module>
>>>      from blueprintcompiler import main
> ...
>>>    File "/usr/lib/python3/dist-packages/blueprintcompiler/gir.py", line 24, in <module>
>>>      import gi # type: ignore
>>> ModuleNotFoundError: No module named 'gi'
> 
> This looks like a missing dependency in blueprint-compiler.
> 
>  From a brief look at the package, it seems like python3-gi might have been
> added to debian/control, instead of adding it to debian/control.in and
> then regenerating debian/control with `make -f debian/rules clean`. This
> effectively results in the change being reverted whenever the package
> is rebuilt.
> 
>      smcv



More information about the pkg-gnome-maintainers mailing list