I have be working on beating the skip broken functionallty in yum in better shape. The was a lot cases were it has to give up. One of the big problems debugging the code is that, repo inconsistencies where skip broken is useful, don’t last long and can be hard to reproduce and retest. So i had been working to make some unit tests in yum, to reproduce the found issues and make the debug output from skip broken a lot better, so it is easier to see what goes wrong.
The current yum in rawhide (3.2.20) is in very good shape and the upstream 3_2_x branch is even better.
If you run into some situation where ‘–skip-broken’ bails out, then please checkout
http://yum.baseurl.org/wiki/SkipBroken
I have just released Yum Extender 2.0.5, not a lot of changes, but a lot of translation updates, thank to all translators and the transiflex maintainers to make it easy for the translator to submit translations upstream.
It is the first release for a long time and the 2.0.x code base is quite stable at the moment and there will only be made bug fixes to the 2.0.x series, no new fancy stuff.
I have started to work on the next generation of yumex, it will be redesigned from scratch, because i want to solve one of the mayor problems in yumex, that the gui get stuck when there is no callback from yum in a long periode of time. so i has started to design a client/server based yum backend there can run in a separete child process and communicate with the gui frontend, using a generic interface. This separation has a lot of benefit and will make it a lot easier to maintain the gui and make it work with different versions of yum or even other package managers.
