reassign 930457 mu-editor thanks (sorry screwed up the headers)

 Ben Nuttal recently informed my that trying to use the "debug" button in 
mu-editor in Debian buster results in

Traceback (most recent call last):

File "/usr/share/mu-editor/mu/mu-debug.py", line 4, in <module>

from mu.app import debug

ModuleNotFoundError: No module named 'mu'

Investigation shows that this is the result of failure to find mu-related 
python modules. mu-editor itself finds them because the mu-editor executable 
(AFTER following the symlink) is located in /usr/share/mu-editor but the 
mu-debug helper script is in a subdirectory and so does not find them.

The simplest fix seems to be to adjust sys.path[0] in mu-debug.py I whipped up 
(and tested) a patch to do that. While working on that I noticed that the clean 
target was broken, so I fixed that too. knowledgejunkie: are you ok if I go 
ahead and NMU this and ask the release team for an unblock? (if I get no 
response i'll NMU in 5 days, but I'd really like to move sooner given how 
little time is available before release)

Reply via email to