I still think this is a bug - ideally they should have set up a transitional "python-support" package requiring the new one as described here: https://wiki.debian.org/Renaming_a_Package
As it is now, I guess packagers have to distribute a .deb for 16.04+ and a separate one for older systems?
I still think this is a bug - ideally they should have set up a transitional "python-support" package requiring the new one as described here: https:/ /wiki.debian. org/Renaming_ a_Package
As it is now, I guess packagers have to distribute a .deb for 16.04+ and a separate one for older systems?