> 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)
Thank you for taking the time to investigate, which confirms my findings after I received the first report of this issue on Sunday in #930270. I have just uploaded mu-editor 1.0.2+dfsg-3 to the PAPT team on salsa which now awaits a sponsored upload to unstable. As I'm in the middle of my NM application it seems like an ideal opportunity for me to push the necessary updates and, post-package-upload, liaise with the release team for the unblock request to get it into buster. Thank you, NIck
