On 03/05/10 21:16, Pierre Chifflier wrote: > Even if I don't exactly care whether if setroubleshoot is included or > not, I'd just like to tell that I find the method quite harsh and > counterproductive. > libgtkhtml2 is unmaintained, that's a fact (that's the case for a big > number of packages, but let's forget it). Helping upstream port it to > libgtkhtml3 would help. Providing patches would help, as giving a > migration path or whatever. Just removing the package will only penalize > users. > Wouldn't filling an RC bug be sufficient to prevent entering testing ?
We don't keep unmaintained and old stuff on unstable forever. If we can remove it, we do it. If that means removing old and unmaintained stuff with it, then we weight the pros and the cons and take action. And in this case, the fact that setroubleshoot has never been part of a stable release is a pro for removing it. As I've said, it can be accepted again after it's ported, and our stable users won't have noticed. Cheers, Emilio -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
