Hi Jeremy, On Thu, Nov 14, 2019 at 07:40:41PM -0500, Jeremy Bicha wrote: > On Wed, Nov 13, 2019 at 3:08 PM Sudip Mukherjee > <sudipm.mukher...@gmail.com> wrote: > > trace-cmd/2.8.3-1 is fixing this as it now uses qt and not pygtk. But > > I am not sure if I should close this bug now or wait for you to verify > > and close it. > > Yes, it was fine that you closed this bug.
Thanks for your reply. I closed it based on reply from "Sandro Tosi" in #938691. > > It looks like trace-cmd still uses Python2 which is (or soon will be) > a Release Critical bug for Bullseye also. I am confused by that. If you see https://packages.debian.org/sid/trace-cmd it shows that it depends of python only for alpha, m68k, powerpcspe, sh4 and if you see the download table on that same page, it shows that those arch (unofficial port) are still using the old version - 2.6.1-0.1 and not this new version. So, I guess, the implication of python2 removal will be that the old version of trace-cmd will be removed from these arch. Am I correct in my understanding? Please correct me if I am wrong. -- Regards Sudip
