Folks,
As upstream maintainer, and on behalf of all the other folks involved in
Mu, I'd just like to say a huge thank you to all involved in reporting,
investigating and fixing this bug.
As fellow open source developers, we're painfully aware of the cost in
time, attention and effort resolving su
> 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 un
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
from mu.app import debug
Package: mu-editor Severity: important x-debbugs-cc: nt...@ntoll.org x-debbugs-cc:
b...@raspberrypi.org x-debbugs-cc: knowledgejun...@gmail.com 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):
Fi
4 matches
Mail list logo
