Cyril Brulebois <k...@debian.org> writes: > Bdale Garbee <bd...@gag.com> (06/02/2013):
>> I personally consider this a regrettable situation, and hope that for >> jessie and beyond we can work out how to do this better. It is >> unacceptable to me to "freeze" anything in sid for more than a week or >> two at a time. Holding d-i's build dependencies static in unstable for >> more than half a year is just nuts to me! > How is that different from e.g. refraining to upload new libraries to > unstable, so that a package needing an upload (say, we need RC bugfixes) > doesn't pick new dependencies (on libraries not in testing)? I personally think it's exactly the same problem. I think the situation with libraries is regrettable as well. (Note that, and I'm guessing I speak for Bdale here too, "regrettable" is not intended to assign any sort of blame! This is the best solution that we've been able to come up with to date as a project. It's just still has some problems.) > That's how testing works; and it's been this way for years/releases now > (since testing replaced frozen, I think). Yes. It's always a source of some tension, since there are always people who would prefer to have a place to continue to do development in an unstable context even during the release process. (Cue the standard debate over the usability of experimental for this purpose -- I'm sure nearly everyone reading this can fill it in from memory. *grin*) If we could find a way to release some of that tension, that would be great, but it's a hard problem, and there's no way that we're going to come up with a solution to it right now in the middle of the wheezy freeze. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
