On Sun, May 29, 2016 at 10:59:47AM +0200, Hector Oron wrote: > Thanks very much for the fix, it just came in the right time. I am > planning to prepare a GDB release soon and I was considering on > dropping gdb-python2. However, now that there seems to be interest on > it, I'd like to know what use cases do you have for gdb-python2 and if > you really think we should release stretch with it and why.
Personally, my motivation was "I'm at a bug squashing party and this looks doable". Sorry, I'm not personally invested in having a python2 variant of gdb. > > I have fixed these in the attached patch and will shortly upload a NMU > > with this fix to DELAYED/5-day. > > It is probably not needed, we (pkg-gdb team) plan to do an upstream > update and few packaging changes. Should I remove the NMU from DELAYED then? Andreas
