[Python-apps-team] Bug#919640: marked as done (mu-editor: Fail to start because matlotlib==2.2.2 is not found)

[Debian Bug Tracking System]

Your message dated Sat, 19 Jan 2019 08:42:39 +0100
with message-id <sa6bm4d3xg0.fsf at meta.reinholdtsen.name>
and subject line Re: Bug#919640: mu-editor: Fail to start because matlotlib==2.2.2 is not found
has caused the Debian Bug report #919640,
regarding mu-editor: Fail to start because matlotlib==2.2.2 is not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
919640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919640
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Petter Reinholdtsen <pere at hungry.com>
Subject: mu-editor: Fail to start because matlotlib==2.2.2 is not found
Date: Fri, 18 Jan 2019 08:42:59 +0100
Size: 2504
URL: <http://alioth-lists.debian.net/pipermail/python-apps-team/attachments/20190119/2fe27172/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Petter Reinholdtsen <pere at hungry.com>
Subject: Re: Bug#919640: mu-editor: Fail to start because matlotlib==2.2.2 is not found
Date: Sat, 19 Jan 2019 08:42:39 +0100
Size: 2938
URL: <http://alioth-lists.debian.net/pipermail/python-apps-team/attachments/20190119/2fe27172/attachment-0001.mht>