Repository navigation
Conversation
Contributor
Author
|
I dropped the conditional nocross in (different wordsize of host and target machines) and was able to build for armv{6,7}l{,-musl} with no further changes necessary locally. Unfortunately I do not have a way to properly test those resulting builds. |
JkktBkkt
force-pushed
the
telegram-cve-fix
branch
from
October 10, 2026 19:07
f7d0404 to
025599d
Compare
JkktBkkt
force-pushed
the
telegram-cve-fix
branch
from
October 10, 2026 19:09
025599d to
001d7aa
Compare
Contributor
Author
|
aarch64-musl failure is unrelated to changes in this PR and that build succeeded with previous push (when the nocross condition was still in the template, which doesn't apply to aarch64-musl builds on x86_64-musl host) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Testing the changes
Local build testing
As seen on https://bugs.gentoo.org/983963#c8, applying just this patch should fix the vulnerability, which means we can postpone packaging 7.2.9+ version of telegram-desktop (doing so is non-trivial due to new dependencies, attempted by ar-jan with LLM use: https://github.com/ar-jan/void-packages/tree/telegram730)
Credit to ar-jan for bringing this issue up.