Hi
Ah, how about instead of working around this, you wait until the deps have been satisfied. I think it's worth saying that we are about to see some humongous changes with the introduction of the module xorg into rawhide (of which these issues are a part) but that, with a little patient a simple 'yum update' should just work. While an 'rpm --nodeps' might _solve_ the problem in the short term, it might also create bigger problems in the long term, making more work for the developers to figure out because someone forced something to 'make it work'. Sorry if this is too harsh, but the use of rawhide needs a little patience sometimes which include putting up with broken deps, broken packages and other stuff. What rawhide doesn't need to 'artificial' breakage that adds another layer of complexity to and already complex task. Rodd
+1 on this. Very well said. regards Rahul -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
