From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: Update poppler to 22.12.0
Date: Tue, 03 Jan 2023 09:11:07 +0100 [thread overview]
Message-ID: <20230103081107.GfhMWKbE30T6RYx59TDqmZWA2JyiixA2k6qKlugSd0I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41070@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]
There's a closed pull request on the void-packages repository
Update poppler to 22.12.0
https://github.com/void-linux/void-packages/pull/41070
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
~~I didn't build libreoffice, but from a quick check it has the patches so it should build.~~
I noticed our current poppler version is affected by CVE-2022-38784. Instead of submiting a patch for that, I decided to go all the way and update to the current stable.
Had to apply patches for inkscape, ipe and scribus.
scribus patch is taken from: https://gitweb.gentoo.org/repo/gentoo.git/plain/app-office/scribus/files/scribus-1.5.8-poppler-22.09.0.patch. The actual upstream commit (https://github.com/scribusproject/scribus/commit/8acd29e97813b9132e3b51b2f05e8fac65819ed7.patch) is slightly different, but does not apply because in between the releases and master, there were additional changes in the file. IMHO scribus could use a release, but nothing we can do.
prev parent reply other threads:[~2023-01-03 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 21:26 [PR PATCH] " crtxcr
2022-12-18 15:53 ` sgn
2022-12-18 20:38 ` crtxcr
2022-12-19 7:07 ` crtxcr
2023-01-03 8:11 ` sgn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230103081107.GfhMWKbE30T6RYx59TDqmZWA2JyiixA2k6qKlugSd0I@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).