More than enough time to close this bug.
Hi,
On Fri, 14 Oct 2016 12:14:56 -0300 Herbert Fortes wrote:
> Hi,
>
> After 10 days on testing I did an
> upload (gifsicle_1.88-2~bpo8+1_amd64.deb)
> to Backports[0].
>
> [0] - https://backports.debian.org/Instructions/
>
It was accepted into jessie-backports today. 2016-10-17
I received the
Hi,
After 10 days on testing I did an
upload (gifsicle_1.88-2~bpo8+1_amd64.deb)
to Backports[0].
[0] - https://backports.debian.org/Instructions/
Regards,
Herbert
fixed 838420 1.88-2
thanks
The upstream applied the patch too.
I think I will do a backport. It is
faster than ask to include a patch
in 'stable'.
Regards,
Herbert
On 26-09-2016 13:39, Herbert Fortes wrote:
> Hi Yuriy M. Kaminskiy,
>
>> Package: gifsicle
>> Version: 1.86-1
>> Severity:
forwarded 838420 https://github.com/kohler/gifsicle/issues/75
thanks
On 20-09-2016 21:40, Yuriy M. Kaminskiy wrote:
> Package: gifsicle
> Version: 1.86-1
> Severity: minor
> Tags: upstream patch
>
> Dear Maintainer,
>
> When showing comment containing non-ASCII characters, `gifsicle -I`
> shows
Hi Yuriy M. Kaminskiy,
> Package: gifsicle
> Version: 1.86-1
> Severity: minor
> Tags: upstream patch
>
> Dear Maintainer,
>
> When showing comment containing non-ASCII characters, `gifsicle -I`
> shows incorrect escape code (\364 instead of \364) on
> platforms with signed char (e.g.
Package: gifsicle
Version: 1.86-1
Severity: minor
Tags: upstream patch
Dear Maintainer,
When showing comment containing non-ASCII characters, `gifsicle -I`
shows incorrect escape code (\364 instead of \364) on platforms
with signed char (e.g. x86{,_64}).
Patches against 1.86 and 1.88
7 matches
Mail list logo
