Package: python3-pygame Version: 1.9.4.post1+dfsg-2 Severity: serious Hi,
your package ships the header file(s): /usr/include/python3.7/pygame/_camera.h /usr/include/python3.7/pygame/_pygame.h /usr/include/python3.7/pygame/_surface.h /usr/include/python3.7/pygame/bitmask.h /usr/include/python3.7/pygame/camera.h /usr/include/python3.7/pygame/fastevents.h /usr/include/python3.7/pygame/font.h /usr/include/python3.7/pygame/freetype.h /usr/include/python3.7/pygame/mask.h /usr/include/python3.7/pygame/mixer.h /usr/include/python3.7/pygame/pgarrinter.h /usr/include/python3.7/pygame/pgbufferproxy.h /usr/include/python3.7/pygame/pgcompat.h /usr/include/python3.7/pygame/pgopengl.h /usr/include/python3.7/pygame/pygame.h /usr/include/python3.7/pygame/scrap.h /usr/include/python3.7/pygame/surface.h but /usr/include/python3.7 is a symlink to python3.7m in libpython3.7-dev. This may result in silent file overwrites or depending on the unpacking order /usr/include/python3.7 being a directory in some cases, separating the headers into two independent trees. These header files must be shipped in /usr/include/python3.7m/ instead. Please talk to the python maintainers to find a proper solution for handling the packaging of python header files in a future-proof way. Cheers, Andreas