On Sat, Feb 14, 2015 at 12:22 PM, Sandro Tosi wrote:
> On Sat, Feb 14, 2015 at 5:13 PM, Michael Gilbert wrote:
>> On Sat, Feb 14, 2015 at 12:03 PM, Sandro Tosi wrote:
Don't the NMU guidelines [0] say otherwise when there is no maintainer
activity for more than 7 days?
>>>
>>> like they
On Sat, Feb 14, 2015 at 5:13 PM, Michael Gilbert wrote:
> On Sat, Feb 14, 2015 at 12:03 PM, Sandro Tosi wrote:
>>> Don't the NMU guidelines [0] say otherwise when there is no maintainer
>>> activity for more than 7 days?
>>
>> like they say "Have you clearly expressed your intention to NMU, at
>>
On Sat, Feb 14, 2015 at 12:03 PM, Sandro Tosi wrote:
>> Don't the NMU guidelines [0] say otherwise when there is no maintainer
>> activity for more than 7 days?
>
> like they say "Have you clearly expressed your intention to NMU, at
> least in the BTS? It is also a good idea to try to contact the
>
On Sat, Feb 14, 2015 at 5:01 PM, Michael Gilbert wrote:
> On Sat, Feb 14, 2015 at 4:59 AM, Sandro Tosi wrote:
>> how about using a delayed queue instead of having uploaded straight to
>> unstable?
>
> Don't the NMU guidelines [0] say otherwise when there is no maintainer
> activity for more than
On Sat, Feb 14, 2015 at 4:59 AM, Sandro Tosi wrote:
> how about using a delayed queue instead of having uploaded straight to
> unstable?
Don't the NMU guidelines [0] say otherwise when there is no maintainer
activity for more than 7 days?
Best wishes,
Mike
[0]
https://www.debian.org/doc/manual
how about using a delayed queue instead of having uploaded straight to unstable?
On Sat, Feb 14, 2015 at 1:35 AM, Michael Gilbert wrote:
> Hi,
>
> I've uploaded an nmu fixing this issue. Please see attached patch.
>
> Best wishes,
> Mike
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My we
Hi,
I've uploaded an nmu fixing this issue. Please see attached patch.
Best wishes,
Mike
diff -Nru matplotlib-1.4.2/debian/changelog matplotlib-1.4.2/debian/changelog
--- matplotlib-1.4.2/debian/changelog 2014-10-30 23:31:05.0 +
+++ matplotlib-1.4.2/debian/changelog 2015-02-14 00:52:
> Thanks for bringing this up again. This should be fixed upstream by:
> https://github.com/matplotlib/matplotlib/commit/ba4016014cb4fb4927e36ce8ea429fed47dcb787#diff-51
This isn't applied yet for 1.4.2 in unstable.
Best wishes,
Mike
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.deb
Thanks for bringing this up again. This should be fixed upstream by:
https://github.com/matplotlib/matplotlib/commit/ba4016014cb4fb4927e36ce8ea429fed47dcb787#diff-51
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.d
Control: retitle -1 matplotlib: CVE-2013-1424: printf buffer overrun
Hi,
On Sun, Jan 18, 2015 at 01:44:36PM -0500, Michael Gilbert wrote:
> package: src:matplotlib
> version: 0.99.3-1
> severity: serious
> tag: security, patch
>
> Matt Giuca reported a matplotlib buffer overrun to the private
>
Processing control commands:
> retitle -1 matplotlib: CVE-2013-1424: printf buffer overrun
Bug #775691 [src:matplotlib] matplotlib: printf buffer overrun
Changed Bug title to 'matplotlib: CVE-2013-1424: printf buffer overrun' from
'matplotlib: printf buffer overrun'
--
775691: http://bugs.debia
package: src:matplotlib
version: 0.99.3-1
severity: serious
tag: security, patch
Matt Giuca reported a matplotlib buffer overrun to the private
security team request tracker in 2013, which ended up falling through
the cracks at the time. See below for the original message and a
proposed patch att
12 matches
Mail list logo
