CC'ing the kdelibs and kdebase maintainer to hear his opinion on the issue. Please keep the CC to #240288.
Clemens Brunner writes: > Hi Dominique! I've been waiting for KDE 3.2.1 to move into Debian > Testing for weeks now, and it finally seemed to happen - until you > filed your fake bug, saying that you thought it was probably not a > good idea to move kdelibs into Testing. Yes, I'm sorry, I should have provided more info in the report, but I had little time when I was writing it. > Could you explain why you filed that bug? kdebase is not yet ready for testing, and it's not a good idea for sarge to have a different kdebase than kdelibs version, for various reasons. I just want to avoid the sarge release hitting us at a point where kdelibs is at 3.2, and kdebase at 3.1. If kdebase is ready, I have no problem with both propagating to testing. > Are there any issues you know about that could result in serious > problems? Or is it just your personal feeling about the package? Just for clarity, I do some work on the package myself, it's not like I have a grudge against KDE or sth like that. > Almost every Linux distribution is now shipping with this latest > version of KDE, and there are no critical bugs that would have > forced the distributors to fall back to an earlier version (like KDE > 3.1.5). > IMO fake bugs are not very sensible, because if there are no known > serious bugs, a package should go into Testing. Except for corner cases like this one, I agree with you. > Then far more people have the possibility to actually test the > package, and that's basically the idea of Debian Testing IMO (moving > things into Stable is, of course, a different story). > I'd be happy if you provided me with some details (especially about > when you estimate that KDE 3.2.1 will finally be merged into Debian > Testing). I hope this clears some things up. Calc, what do you think ? cheers domi
