<br><br><div class="gmail_quote">On Sat, Dec 6, 2008 at 12:28, Horst H. von Brand <span dir="ltr"><<a href="mailto:vonbrand@inf.utfsm.cl">vonbrand@inf.utfsm.cl</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Ignacio Vazquez-Abrams <<a href="mailto:ivazqueznet@gmail.com">ivazqueznet@gmail.com</a>> wrote:<br>
> Python 2.6 is now in Rawhide and ready to be battle-tested. Tools up to<br>
> yum and system-config-* work, with some DeprecationWarnings;<br>
> higher-level tools are still being worked on.<br>
<br>
</div>I have dozens of packages that can't be upgraded (including yum and rpm)<br>
now. Any (simple) way to find out what the offending packages are?<br>
</blockquote></div><br>If you're running yum upgrade by hand you can look at the yum output. Right after it has gotten all the packages it runs the dependency checking.<br><br>Usually the packages that yum mentions again at the tail of the output are the ones with issues.<br>
<br>In my case, I had to remove system-config-httpd, alchemist, libopensync and python-turboflot. I don't think the first pair has been updated yet and the latter didn't seem to be used by anything. You'll probably have different packages with issues.<br>
<br>After that, I'm running just fine on today's rawhide.<br><br>darrell<br>