2010/6/14 Yaakov (Cygwin/X): > On Sat, 2010-06-12 at 21:09 -0400, Jason Tishler wrote: >> Well, it's more "about" than "on," but I'm ready to release Python >> 2.6.5-2 and promote it to current. >> >> However, AFAICT, most of the above packages have not been rebuilt >> against Python 2.6.5-1. Should I release and promote Python 2.6.5-2 >> anyways? Or, should I wait for more of the above to be updated first? > > Personally, my packages (both distro and Ports) are ready to go, and I'm > getting tired of being in limbo. OTOH, things will break if we switch > before everything else is ready. > > I'm most concerned about Jari's packages. bzr and mercurial are pretty > important, and python-crypto, python-feedparser, and python-paramiko are > dependencies of other packages. Unfortunately, the last we heard from > him on this was not encouraging. > > I think we need some guidance from cgf and Corinna on this one: at what > point can we say that a package has been orphaned, at least to the point > that we can do a one-time NMU in order to not break the distro, if not > an outright adoption?
I'm planning to get postgresql-9.0 ready. But I have problems with my eyes, so I don't have that much time to work on this as I thought. I hope next week it will be over and my right eye is functional again -- Reini Urban http://phpwiki.org/ http://murbreak.at/
