for all maintainers of packages which BuildRequire qt4-devel (or qt-devel, but
the versioned virtual Provides is preferred): please, when you plan to push
updates for your packages, ALWAYS CHECK what version of Qt your package got
built against and DO NOT PUSH your update to stable before that version of Qt
goes stable! A package built against Qt 4.6 WILL NOT WORK AT ALL with Qt
4.5!!! (This is always the case, Qt is backwards- but not forwards-
Currently, buildroot overrides for Qt 4.6 are in effect (intermittently, as Qt
4.6 can and will be untagged from the buildroot on request to build updates
which need to go out soon, but we need it in the buildroot to build anything
related to KDE 4.4), so a package built now CANNOT go to stable before the big
Qt 4.6 / KDE 4.4 / SIP 4.10 update does. If you need to push an urgent update,
please ask Rex Dieter (rdieter on Freenode IRC) or another rel-eng member to
get the stuff out of the buildroot for a moment, and follow the instructions
given on IRC. If your update is not urgent, I recommend just not pushing it
out to stable before the big Qt/KDE/SIP update.
NOT FOLLOWING THOSE INSTRUCTIONS WILL LEAD TO YOUR PACKAGE BEING BROKEN IN THE
STABLE UPDATES!!! YOU HAVE BEEN WARNED!
I am sorry if I sound abrasive, but we already had at least 2 packages which
were broken due to this issue (just for 4.6, there were more such issues with
previous upgrades) and it looks like our previous devel-announce message was
not clear enough. Please double-check before you hit that "push to stable"
button! Thanks in advance.
We will look into using some less dangerous process (special build tags?) for
future Qt updates as this is just not working, but for now please be careful.
Show replies by date