In the build log we see: Merged Build-Depends: ..., python-gtk2 (<< 2.10) | python-gobject, ... Filtered Build-Depends: ..., python-gtk2 (<< 2.10), ...
So before it even tried to install dependencies, it pruned out all the alternatives. When the first alternative failed, it didn't go back and try the other alternative that would have worked. 1) Is there a rule that says that the first depedency in a list of alternatives MUST work? 2) If not, isn't this a bug in / limitation of sbuild? 3) If it's not a bug, but a known limitation, shouldn't this not be used to indicate the buginess of other packages? Anyway, the fix or workaround (whichever it is) is probably just to reorder to put python-gobject first in the dependency list.
signature.asc
Description: This is a digitally signed message part.
