On Sun, 2011-11-20 at 12:51 +0100, Mehdi Dogguy wrote: > On 11/20/2011 12:17 AM, Adam D. Barratt wrote: > > On Thu, 2011-11-17 at 20:54 +0000, Adam D. Barratt wrote: > >> On Sun, 2011-04-10 at 15:36 +0200, Mehdi Dogguy wrote: > >>> It seems that britney2 segfaults at every run when compiled for Python > >>> 2.6. After some quick investigation, the problem boils down to the > >>> following: > > [...] > >> I've finally (!) got to looking at this but have been unable to > >> reproduce the problem. It might be a squeeze versus wheezy issue or > >> some oddity which has resolved itself in the meantime, but after > >> s/python2.5/python2.6/ in britney-py.c and rebuilding the library on > >> franck, everything seems to just work[tm]. [...] > maybe we should close the bug then? (it could be a temporary problem that > got fixed somewhere since then…)
I was planning on running a py2.6 britney live for a couple of days and seeing what happened first; what's the worst that could happen? :) Switching to 2.6 would also get us some other advantages (along with making DSA happy), like the nicer property decorator syntax. > P.S.: I'll keep all packages infos next time :/ Thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
