Hello Andreas and Ben, 2016-05-28 18:50 GMT+02:00 Andreas Bombe <[email protected]>: > On Tue, Sep 08, 2015 at 12:59:06PM -0700, Ben Longbons wrote:
>> The gdb-python2 package does not actually contain a version of gdb >> linked to python2. Rather, it is a byte-for-byte identical copy of the >> /usr/bin/gdb shipped in the gdb package, which links to python3. >> >> I noticed that gdb-python2 has "Depends: libpython3.4", I presume this >> is automatic from the list of linked shared libs. > > I have verified on snapshot.debian.org that gdb-python2 has been broken > since it was introduced. Basically the python2 linked version gets built > and then ignored. There were more problems such as files missing in > gdb-python2. 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. > 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. Please let me know your gdb-python2 use case, that'd be quite helpful. TIA. Best regards, -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.
