Bug#1006009: fixed in libwebp 1.2.2-1

2022-03-13 Thread Jeff Breidenbach 
Yes, I made a mistake with respect to 1.2.2. Upstream's official patch is
here. I am going to attempt a high urgency upload during the next houw with
1.2.2 + this patch. If that fails for any reason, NMU welcome without
delay.

https://chromium.googlesource.com/webm/libwebp/+/4f1839957115fa4713ed745ceb898657361a1195

>

Bug#1006009: fixed in libwebp 1.2.2-1

2022-03-13 Thread Andres Salomon 

Hi Jeff,

I'm planning to a NMU of libwebp in 2 days (Tues Mar 15th) to fix this 
bug, if you lack the time to fix it before then.


Thanks,

Andres


On 3/13/22 01:22, Jeremy Bicha wrote:

Please set the urgency to high when you do the upload to fix the new 
regression. That will automatically reduce the time to migrate to 
testing to 2 days since this transition has been open for several 
weeks now.


Thank you,
Jeremy Bicha

Bug#1006009: fixed in libwebp 1.2.2-1

2022-03-12 Thread Jeremy Bicha 
Please set the urgency to high when you do the upload to fix the new
regression. That will automatically reduce the time to migrate to testing
to 2 days since this transition has been open for several weeks now.

Thank you,
Jeremy Bicha

Bug#1006009: fixed in libwebp 1.2.2-1

2022-03-12 Thread Dmitry Shachnev 
Control: reopen -1
Control: found -1 libwebp/1.2.2-1

Hi all,

On Thu, Mar 10, 2022 at 11:17:50PM -0500, Andres Salomon wrote:
> Hi,
>
> Are you sure that 1.2.2 fixes the build failure?  The 1.2.2 release was
> tagged on Jan 20th:
>
> https://chromium.googlesource.com/webm/libwebp/+/refs/tags/v1.2.2
>
> The MIPS regression wasn't reported until Feb, and the commit that fixed it
> was made on March 1st:
>
> https://bugs.chromium.org/p/webp/issues/detail?id=558
>
> https://chromium.googlesource.com/webm/libwebp/+/e4cbcdd2b5ff33a64f97fe49d67fb56f915657e8%5E%21/
>
> So it would remain unfixed in 1.2.2-1 unless you patched something else to
> fix it? I don't see that particular commit in the uploaded source:
>
> https://sources.debian.org/src/libwebp/1.2.2-1/src/dsp/lossless_enc_mips32.c/

Indeed, with 1.2.2-1 this bug appears again:

https://buildd.debian.org/status/fetch.php?pkg=qtimageformats-opensource-src=mipsel=5.15.3-1=1647075018=0

Please add back the patch from NMU which was dropped.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1006009: fixed in libwebp 1.2.2-1

2022-03-10 Thread Andres Salomon 

On Thu, 10 Mar 2022 18:19:09 + Debian FTP Masters wrote:

> Changes:
> libwebp (1.2.2-1) unstable; urgency=medium
> .
> * New upstream release.
> * Fixes test failure on mipsel architecture (closes: #1006110)
> * Fixes test failure on mipsel architecture (closes: #1006009)
> Checksums-Sha1:
> fa0dc9d5c407167d48faaf9b057f28afd11a6fef 2065 libwebp_1.2.2-1.dsc
> 4e5e570b1ece450ec38233c52adbae253f81127e 4117468 
libwebp_1.2.2.orig.tar.gz


Hi,

Are you sure that 1.2.2 fixes the build failure?  The 1.2.2 release was 
tagged on Jan 20th:


https://chromium.googlesource.com/webm/libwebp/+/refs/tags/v1.2.2


The MIPS regression wasn't reported until Feb, and the commit that fixed 
it was made on March 1st:


https://bugs.chromium.org/p/webp/issues/detail?id=558

https://chromium.googlesource.com/webm/libwebp/+/e4cbcdd2b5ff33a64f97fe49d67fb56f915657e8%5E%21/

So it would remain unfixed in 1.2.2-1 unless you patched something else 
to fix it? I don't see that particular commit in the uploaded source:


https://sources.debian.org/src/libwebp/1.2.2-1/src/dsp/lossless_enc_mips32.c/


Thanks,

Andres