Bug#844924: pygobject: FTBFS: Tests failures

[Michael Biebl]

Am 19.11.2016 um 08:03 schrieb Lucas Nussbaum:
> Source: pygobject
> Version: 3.22.0-1
> Severity: serious
> Tags: stretch sid
> User: debian-qa at lists.debian.org
> Usertags: qa-ftbfs-20161118 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
>> if 'generic-c-marshaller' in GObject.features:
>> ^
>> pygtkcompat/pygtkcompat.py:102:1: E305 expected 2 blank lines after class or function definition, found 1
>> _unset = object()
>> ^

Looks like pep8 got stricter (again).
There were some new upstream releases just recently.
I got some build failures in other packages as well.

Somehow I think it would be good to avoid such uploads so close to the
freeze or better coordinate uploads of pep8.

Would it be possible to re-compile reverse build-dependencies of pep8
before a new major upstream release? Somehow this feels like it should
be treated like a (library) transtion.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20161120/9eb3c396/attachment-0001.sig>