[poppler] Update to 22.09.0.

[attah]

WIP: depends on jpeg_mem_src, and i have yet to figure out how to update in the sdk.
Minor freshening up of the Qt compat patch.

[vigejolla]

WIP: depends on jpeg_mem_src, and i have yet to figure out how to update in the sdk.
Minor freshening up of the Qt compat patch.

Yeah, you should first get the jpeg_mem_src change in. And then I think you should change the BuildRequire to libjpeg-turbo-devel >= 2.1.0+git2, as this change depends on a change introduced there. It's unfortunate that pkgconfig versioning only goes to the "2.1.0" level. The "update in the sdk" part is easy, you just need to use shared output directory for both projects.

[pvuorela]

The patch seems to have accumulated some offset with the upstream. Would be nice if you recreated that. Apply to git and then export back to file. git format-patch with --no-numbered --zero-commit

[Thaodan]

The patch seems to have accumulated some offset with the upstream. Would be nice if you recreated that. Apply to git and then export back to file. git reformat-patch with --no-numbered --zero-commit

Please use: format-patch --no-numbered --zero-commit --no-signature --full- index

[attah]

Re-exported patch, added another to not build demos since they now use qt 5.7 stuff, and updated the version in spec.
Should there be a Requires for libjpeg-turbo too?
Installed and seems to work fine on my phone, but have not done any formal testing.

[Thaodan]

Re-exported patch, added another to not build demos since they now use qt 5.7 stuff, and updated the version in spec. Should there be a Requires for libjpeg-turbo too? Installed and seems to work fine on my phone, but have not done any formal testing.

No never unless the dependency generator for your language isn't packaged. RPM will resolve any dependency.

[attah]

And of course there has been a new release, with a fix for a pretty nasty CVE (FORCEDENTRY-related).
Would it be ok if i updated this PR to 22.09 even if that means mismatching the branch name? (Which i guess doesn't actually show, just influence what the suggested merge message is)
Or do you want a replacement PR, another PR on top, or just handle it from your end?

[pvuorela]

Just update this one, fine as long as the commit message matches the content.

[pvuorela]

Looking good.