pygobject fails to build in Ubuntu 18.10

Bug #1787474 reported by Jeremy Bicha on 2018-08-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
glib2.0 (Ubuntu)
Undecided
Unassigned
pygobject (Ubuntu)
Undecided
Unassigned

Bug Description

pygobject 3.28.2-1 and 3.29.2-1 fails to build in Ubuntu 18.10.

pygobject 3.28.2-1 does build successfully on Ubuntu 18.04 LTS. 3.29.2-1 does build successfully in Debian unstable.

I confirmed that the problem is reproducible in a local sbuild. I confirm that the test hang also happens with python 3.7.

By the way, I had to manually cancel the builds since they were still hanging after 20 hours.

Build log
---------
https://launchpad.net/ubuntu/+source/pygobject/3.29.2-1/+build/15263898

Build log excerpt
-----------------

I: pybuild base:217: cd /<<PKGBUILDDIR>>/.pybuild/cpython2_2.7/build; python2.7 -m pytest tests
============================= test session starts ==============================
platform linux2 -- Python 2.7.15, pytest-3.6.4, py-1.5.4, pluggy-0.6.0
rootdir: /<<PKGBUILDDIR>>, inifile:
collected 1374 items

tests/test_atoms.py ....... [ 0%]
tests/test_cairo.py ......................... [ 2%]
tests/test_docstring.py ...............x. [ 3%]
tests/test_error.py ............... [ 4%]
tests/test_everything.py Trace/breakpoint trap (core dumped)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=133: cd /<<PKGBUILDDIR>>/.pybuild/cpython2_2.7/build; python2.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned exit code 13
make[1]: *** [debian/rules:29: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:22: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
RUN: /usr/share/launchpad-buildd/slavebin/in-target scan-for-processes --backend=chroot --series=cosmic --arch=amd64 PACKAGEBUILD-15263898
Scanning for processes to kill in build PACKAGEBUILD-15263898
Build killed with signal TERM after 150 minutes of inactivity

Jeremy Bicha (jbicha) on 2018-08-16
description: updated
Jeremy Bicha (jbicha) wrote :

Oh maybe this is just incompatibility with the new glib. There was a new pygobject release today.

Christoph Reiter (lazka) wrote :

I think this is https://gitlab.gnome.org/GNOME/gobject-introspection/commit/1f5c81048d762f4866137e1e3221d85b9b611d8b which isn't in a release yet. I'll ask for a release.

I also noticed that the pygobject test suite fails due to sys.excepthook == apport_excepthook, I'll look into that.

Christoph Reiter (lazka) wrote :

We do test against gnome master now with gitlab-CI, so hopefully this will be noticed earlier in future releases.

Christoph Reiter (lazka) wrote :

New 1.57.3 g-i tarball is out.

For the apport thing (I'm not sure if this is relevant in your build environment): https://gitlab.gnome.org/GNOME/pygobject/commit/d9ddad7bcac86d37a9010c8cd529a0e6ca1a9f48

PyGObject tests might still fail because of https://gitlab.gnome.org/GNOME/glib/commit/0319dac01d64f9f95cf84c511a1679ba469e6cbb -> needs a new glib release.

Jeremy Bicha (jbicha) wrote :

Thank you. After updating gobject-introspection to 1.57.3, pygobject builds successfully.

https://launchpad.net/ubuntu/+source/pygobject/3.29.2-1

Changed in pygobject (Ubuntu):
status: New → Fix Released
Jeremy Bicha (jbicha) wrote :

Well it still fails on s390x, so I guess I'll reopen this bug instead of filing a new LP bug.

I also opened https://gitlab.gnome.org/GNOME/pygobject/issues/247

Changed in pygobject (Ubuntu):
status: Fix Released → New
Jeremy Bicha (jbicha) on 2018-08-20
Changed in glib2.0 (Ubuntu):
status: New → Fix Committed
Jeremy Bicha (jbicha) on 2018-08-21
Changed in glib2.0 (Ubuntu):
status: Fix Committed → Fix Released
Jeremy Bicha (jbicha) wrote :
Changed in pygobject (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers