>What does the comment "but m68k isn't keeping up, so nevermind" mean, >and is it still true?
I dunno, but m68k *is* behind. There's a bug in kdelibs which is m68k-specific (a crash in 'meinproc'), which needs to be tracked down before kde can go into testing. This exhibits itself during building of kdeedu. All kde builds are currently delayed until the latest qt package is built on m68k (the only arch it currently needs). That's building right now, and has been for about 12 hours... It'll probably be days before we even have verification that the bug still exists. This is the last genuine bug which has been keeping most of kde out of testing since openldap2 went in (the others are NMU-fixed). If it does still exist, there will likely have to be more kde rebuilds to test fixes. kdebase apparently takes upwards of 100 hours (!) to build on m68k... So m68k has become the bottleneck for KDE to get into testing. If a concerted effort is made to deal with that, it will probably slow down the building of everything else on m68k, of course... I'm sure it will catch up eventually, but it does seem to be behind right now. -- Nathanael Nerode <neroden at gcc.gnu.org> http://home.twcny.rr.com/nerode/neroden/fdl.html