<snip>
> I don't use yumex much myself but I thought you may want to check if it still 
> uses the wrong populateSack() api which doesn't work in sl51, ie calling 
> populateSack(mdtype=...) rather than populateSack(with=...).
>
> A quick check on an sl51 box here shows just yumex and the yum changelog 
> plugin obviously using the wrong api:
>
> $ locate .py| xargs egrep 'populateSack.*mdtype'
> /usr/lib/yum-plugins/changelog.py: 
> repos.populateSack(mdtype='otherdata')
> /usr/share/yumex/yumapi.py: 
> self.repos.populateSack(mdtype='filelists')
> /usr/share/yumex/yumapi.py: 
> self.repos.populateSack(mdtype='otherdata')
>
> currently I hack the /usr/lib/python2.4/site-packages/yum/repos.py from 
> yum-3.0.6-3.sl.noarch to recognise either with=... or mdtype=... options, 
> since I want the yum --changelog option to work.
>
> I'll hopefully soon be able to check on a test 5rolling install since it has 
> a much newer yum things may be different there...

On a test sl5rolling (i386) install all the .py files I got now seem to 
use the:

   ...populateSack(mdtype=...)

form which seems to be what the repos.py from yum-3.2.8-10.sl.noarch now 
accepts.  ie it looks like it is consistent again.

Now I just need to figure out:

   how to drive this new mpi-selector thingy (for example should I do
   something with it for our local mpich package...)

   how to fix our scripts which tweak the ffox/tbird configs

   which other packages clash with changes we have made elsewhere... :-(

It all looks very good so far!!

  -- Jon