Stuart Prescott

In https://bugs.debian.org/885493 the Debian PyGTK maintainers indicate that they do not wish to have PyGTK in the next release; removal from Debian derivatives would presumably follow. I would be hoping...

> am curious as to a use case where this is high impact I'm currently looking at a bug that can be fixed with setuptools > 60 but the runtime...

Thanks @stuartarchibald; removing the run-time dependency on setuptools for the build-tool still seems like something to investigate regardless.

> Broken with Ubuntu 22.04 LTS, too. Whoever packaged this for Debian/Ubuntu never bothered to try opening even a single .po file with it because it would have been obvious...

Rather than having iso-codes from Debian get slurped into this project and then get excised once again to make a pycountry upload to Debian, perhaps the iso-codes package and this...

Hi @nschimmoller! > > "... then get excised once again to make a pycountry upload to Debian..." > > Can you explain more of what you mean by this? To...

Writing on behalf of the python-debian maintainer team: We want python-debian to be portable and widely usable. We definitely don't want people to feel the need to fork it, particularly...

This (and the other "Permission denied" duplicates) appears to be due to the change in selinux from permissive to enforcing in KitKat. The selinux context of all the files shipped...