Your message dated Sat, 6 Jul 2013 23:43:59 +0200
with message-id
<CAB4XWXz293yio28EPMSDwfrvz26Ya9-=ed4r83zf4uhzeno...@mail.gmail.com>
and subject line Re: [Python-modules-team] Bug#699528: python-matplotlib: PDF
renderer draws strange artifacts on '%' character in matplotlib 1.1.1
has caused the Debian Bug report #699528,
regarding python-matplotlib: PDF renderer draws strange artifacts on '%'
character in matplotlib 1.1.1
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 [email protected]
immediately.)
--
699528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699528
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-matplotlib
Version: 1.1.1~rc2-1
Severity: normal
Hi all,
This is a known bug from matplotlib 1.1.1, see
https://github.com/matplotlib/matplotlib/issues/1211
It is very annoying since many plot include % signs. An update to matplotlib
1.1.2 for wheezy should thus be made soon.
regards, Juergen
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python-matplotlib depends on:
ii libatk1.0-0 2.4.0-2
ii libc6 2.13-35
ii libcairo2 1.12.2-2
ii libfontconfig1 2.9.0-7
ii libfreetype6 2.4.9-1
ii libgcc1 1:4.7.2-4
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-0 2.33.12+really2.32.4-3
ii libgtk2.0-0 2.24.10-2
ii libpango1.0-0 1.30.0-1
ii libpng12-0 1.2.49-2
ii libstdc++6 4.7.2-4
ii python 2.7.3~rc2-1
ii python-cairo 1.8.8-1+b2
ii python-dateutil 1.5+dfsg-0.1
ii python-gobject 3.2.2-1
ii python-matplotlib-data 1.1.1~rc2-1
ii python-numpy [python-numpy-abi9] 1:1.6.2-1
ii python-pyparsing 1.5.6+dfsg1-2
ii python-support 1.0.15
ii python-tz 2012c-1
ii tcl8.5 8.5.11-2
ii tk8.5 8.5.11-2
ii zlib1g 1:1.2.7.dfsg-13
Versions of packages python-matplotlib recommends:
ii python-glade2 2.24.0-3
ii python-tk 2.7.3-1
Versions of packages python-matplotlib suggests:
pn dvipng <none>
ii ipython 0.13.1-2
ii librsvg2-common 2.36.1-1
ii python-configobj 4.7.2+ds-4
pn python-excelerator <none>
ii python-gtk2 2.24.0-3
pn python-matplotlib-doc <none>
pn python-qt4 <none>
ii python-scipy 0.10.1+dfsg1-4
pn python-traits <none>
pn python-wxgtk2.8 <none>
ii texlive-extra-utils 2012.20120611-2
ii texlive-latex-extra 2012.20120611-2
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.2.0-1
On Fri, Feb 1, 2013 at 11:07 AM, Juergen Fuchsberger
<[email protected]> wrote:
> This is a known bug from matplotlib 1.1.1, see
This has been fixed with the aforementioned upload.
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
_______________________________________________
Python-modules-team mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
