Hello, it is needed for new libavif, as explained in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022001
Having the new version will make easier to build it with finally the
sharpyuv functionality.
That said, will be anyway autosync next time we open, so there should be
plenty of time to
What's the rational to want to push for a newer version at this point of
the cycle and what sort of testing was done to ensure it's not including
potential regressions? The security fixes are included as patches in the
current package revision...
--
You received this bug notification because you
** Changed in: libwebp (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libwebp in Ubuntu.
https://bugs.launchpad.net/bugs/2037527
Title:
[Ffe] libwebp
Status in libwebp package in
** Changed in: libwebp (Ubuntu)
Assignee: Ubuntu Release Team (ubuntu-release) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libwebp in Ubuntu.
https://bugs.launchpad.net/bugs/2037527
Title:
[Ffe]
** Description changed:
- 9/13/2023: version 1.3.2
- This is a binary compatible release.
- * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863)
+ This is a binary compatible release.
+ * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863)
-
5 matches
Mail list logo
