Red Hat Bugzilla – Bug 855346
Last modified: 2015-07-10 16:04:45 EDT
Description of problem:
firewalld uses gi/gobject. This isn't in and of itself a problem.
However, using this leads to a dep on pygobject3, which starts bringing in:
all from firewalld just wanting to use the mainloop and the Gio file monitor.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. yum groupinstall core standard
Hey, where did the GUI stuff come from?
Looks like it can be 'fixed' by subpackaging out /usr/lib64/python2.7/site-packages/gi/_gi_cairo.so into a different package.
Do we know which packages require the python Cairo gi? As these would have to be changed to require the subpackage.
It's worth noting that pygobject already has a build-time option to disable the cairo bindings; that helps people building embedded systems and the like.
I'm not sure though if there's much to do upstream to help - I doubt it's worth having a properly defined/documented extension mechanism just for this, since cairo is a special case; the combination of gobject-introspection/pygobject are the generic plugin system basically.
pygobject3-3.4.2-4.fc18,firewalld-0.2.11-2.fc18 has been submitted as an update for Fedora 18.
Package pygobject3-3.4.2-4.fc18, firewalld-0.2.11-2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing pygobject3-3.4.2-4.fc18 firewalld-0.2.11-2.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
pygobject3-3.4.2-4.fc18, firewalld-0.2.11-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.