Thanks to MikeC for the references. The situation is as follows. The PR1.2 release process got borked, and developers (myself included) got caught in the gap. To avoid further mixups, delays, depending on the Qt packaging strategy, I will reconsider my decision to have a single packageset, so you will probably be seeing python2.5-qt4-* compiled for the current PR and a python2.5-qt4-devel-* which will be compiled against the Qt version in extras-devel. Sadly (unlike Qt) you will not be able to have both installed simultaneously. It's not too nice, but since it looks like the Qt4.7 release is going to use the same procedure as Qt4.6, that seems the lesser evil Oh, and I did not make any X86 debs, sorry, will remedy that shortly (though it is more likely that I end up uploading it to extras-devel according to the scheme specified above).