Control: severity -1 wishlist Control: retitle -1 consider devendoring pmw module
The bkchem package is functional without a separate python3-pmw package as it is carrying its own vendored version of pmw: $ dpkg -L bkchem|grep -i pmw /usr/share/bkchem/bkchem/Pmw.py /usr/share/bkchem/bkchem/PmwBlt.py /usr/share/bkchem/bkchem/PmwColor.py Bundling pmw into the application is one of the intended modes of use of this module, with the pmw sources including a "bundlepmw.py" script that generates the files included in bkchem. For bkchem we can then either: 1. carefully check through the quite large divergence between pmw upstream and bkchem's vendored version of pmw (some 41 commits in bkchem git) 2. package python3-pmw 3. wait for it to go through NEW 4. devendor pmw (note that is not just a matter of deleting the files) 5. depend on the python3-pmw package instead or 1. do nothing to bkchem. (that doesn't preclude updating python3-pmw for #886617 anyway, just that bkchem wouldn't use it) There is one other potential user of a python3-pmw package in Debian and that is the auto-07p package. Like bkchem, the auto-07p git history shows modification of the bundled pmw making devendoring hard. regards Stuart -- Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7