Hi! > thanks a lot, but what about backports. On backports we still need this > mapping. Aren't the backports built using the dh-python version of the platform they are ported to? In this case it shouldn't really matter right?
I see that Ubuntu released a new dh-python with this exact fix. It seems to work fine. Right now the packages we push with the pylint3 dependency renamed still end up with pylint3 as dependency, so should we hold off on the auto-pylint transition until https://salsa.debian.org/python-team/tools/dh-python/merge_requests/9 is merged and release? Or is an automatic rebuild of the packages having that problem planned when that fix in dh-python is release? Thanks, Joseph