hi all, the purpose of this mail is to explain to the Release Team the (straightforward) proposal that the KDE Team has come up with to ensure a safe transition of KDE 3.3 to sarge.
in a nutshell, the intention is the same as that of some weeks ago: let it happen all at once. to address Steve's concerns that some external factor (e.g., a lately reported serious bug) could affect the transition, we plan on uploading a new kdelibs 3.3.1-2 package that will conflict with versions << 4:3.3.0 of all the official KDE metapackages (1). (1) which are: kdeaccessibility kdeaddons kdeadmin kdeartwork kdebase kdebindings kdeedu kdegames kdegraphics kde-i18n kdemultimedia kdenetwork kdepim kdesdk kdetoys kdeutils kdewebdev. then, britney will allow either all of these packages to enter, or none, since allowing kdelibs alone would make the rest uninstallable in sarge. * * * now for the verbosity and the details: we are aware that such conflicts only address the transition and not the whole user-can-end-with-mixed-installed-versions issue. as we have previously stated, we prefer to deal with that problem later, probably post-sarge. having the transition done this way: (a) won't make the situation of KDE in sarge any worse dependency-wise and (b) permits us to be confident that the transition is possible, given the good shape of KDE builds ATM. * * * when can the transition happen? well, once we get RMs' approval to the plan, we will upload kdelibs 3.3.1-2 with urgency=medium, and then some RM will have to (or instruct us to) close #266478 ("new kdelibs should not enter testing alone"). other than that, see migration-status.txt [1] if interested, to see the overall situation of KDE packages' builds. [1] http://pkg-kde.alioth.debian.org/migration-status.txt * * * thanks. -- dato, on behalf of the KDE Team. -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 The first step on the road to wisdom is the admission of ignorance. The second step is realizing that you don't have to blab it to the world.