I had the same kind of dependency problems with X11 on my rawhide. To solve that:<div> first i listed the installed x11 rpm and kept the list in a file for potential further usage (i had 42 packages)</div><div>then i boot in single line mode </div>
<div>then delete all the X11 rpm-s</div><div>then re-install them starting x11 server</div><div>then restart and everything worked fine</div><div><br></div><div>Of course this is not the normal way but with rawhide you sometime have to use the caterpillar method.<br>
<br><div class="gmail_quote">On Thu, Dec 22, 2011 at 5:52 PM, Bruno Wolff III <span dir="ltr"><<a href="mailto:bruno@wolff.to">bruno@wolff.to</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Thu, Dec 22, 2011 at 16:46:30 +0000,<br>
Andre Robatino <<a href="mailto:robatino@fedoraproject.org">robatino@fedoraproject.org</a>> wrote:<br>
> Bruno Wolff III <bruno <at> <a href="http://wolff.to" target="_blank">wolff.to</a>> writes:<br>
><br>
> > When that first showed up I just removed the offending packages, did an<br>
> > update and things worked. The problem might be hardware related.<br>
><br>
> Can you be more specific as to "offending packages"? If making this work<br>
> requires removing dozens of packages, I'd rather continue using multiuser mode<br>
> and wait for the problem to get fixed.<br>
<br>
</div>What I do for key packages that I don't want to uninstall because they'd<br>
take most of the system with them is get the list of conflicts from the<br>
rawhide report, remove version and extra white space, remove duplicates<br>
and then use yum to find the ones I have installed and remove those. I add<br>
the list of stuff removed to a list i use to keep track of removed packages.<br>
(I generally prefer running up to date stuff over keeping packages that<br>
block updates, installed.) The rawhide reports don't cover rpmfusion<br>
packages, so if those are blocking updates you'll need to find them another<br>
way. Sometimes you can tell which packages are blocking updates just by<br>
looking at the normal yum output. Using -v helps in some other cases, but<br>
even with -v it isn't always clear which packages are causing problems.<br>
<br>
For packages that are key dependencies, you can just remove them and then<br>
try to put everything back.<br>
<div class="HOEnZb"><div class="h5">--<br>
test mailing list<br>
<a href="mailto:test@lists.fedoraproject.org">test@lists.fedoraproject.org</a><br>
To unsubscribe:<br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/test" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/test</a></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Bruno Gardin<br>
</div>