On Tue, Jan 27, 2026 at 9:01 PM Gyorgy Sarvari via lists.openembedded.org <[email protected]> wrote: > > > This patch-series looks straightforward, but unfortunately this is not the > case, > at least policy-wise. > > Trying to be short. TigerVNC compiles its own Xserver, not the one from > oe-core. > > This series: > -Update xserver to latest dot release of 1.20.x series > -Add patches to all outstanding CVEs that are associated with TigerVNC > -There are unpatched CVEs which are not associated with TigerVNC > -This xserver version is different from the one in oe-core > -Complies with stable-branch policy > > Alternative: > -Cherry-Pick some patches from master[1] > -The xserver version jump would be a major one (1.20.x -> 21.x) > -It would get TigerVNC's xserver in sync with oe-core's xserver > -Have all known xserver fixes without carrying patches > -One might argue that this ship has sailed when Scarthgap was branched off > > The same problem is present in Kirkstone also - whatever happens in Scarthgap > will be cherry-picked in Kirkstone also. > > Anyone has any input on this? I'm especially hoping that some TigerVNC users > will see this, but I'm happy for all feedback.
I think it should use the same version so it works. It should be considered as a bug in the recipe. Thanks, Anuj
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#123983): https://lists.openembedded.org/g/openembedded-devel/message/123983 Mute This Topic: https://lists.openembedded.org/mt/117487426/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
