Skip to content

TigerVNC: update builtin xorg-server to 21.1.17 #11418

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 18, 2025

Conversation

Dustymind
Copy link
Member

@Dustymind Dustymind commented Jun 18, 2025

Topic Description

  • topics: add tigervnc-1.15.0-xserver21.1.17.toml
  • tigervnc: update builtin xorg-server to 21.1.17

Package(s) Affected

  • tigervnc: 1.15.0+xserver21.1.17

Security Update?

Yes, #11415

Build Order

#buildit tigervnc

Test Build(s) Done

Primary Architectures

  • AMD64 amd64
  • AArch64 arm64
  • LoongArch 64-bit loongarch64

Secondary Architectures

  • Loongson 3 loongson3
  • PowerPC 64-bit (Little Endian) ppc64el
  • RISC-V 64-bit riscv64

@Dustymind Dustymind added the upgrade Topic/issue involves a package upgrade label Jun 18, 2025
@aosc-buildit-bot
Copy link
Contributor

Dickens-topic report:

tigervnc upgraded from 1.15.0+xserver21.1.16 to 1.15.0+xserver21.1.17~pre20250618T102923Z on amd64, arm64, loongarch64, loongson3, ppc64el, riscv64:

No changes, size +18.2 KB (+0.1%)

@Dustymind
Copy link
Member Author

TUM:
image

@Dustymind
Copy link
Member Author

LGTM on arm64:
image

@Dustymind Dustymind marked this pull request as ready for review June 18, 2025 11:21
@Dustymind Dustymind force-pushed the tigervnc-1.15.0-xserver21.1.17 branch from e816d15 to 61c5dec Compare June 18, 2025 11:48
@Dustymind Dustymind merged commit c9712e1 into stable Jun 18, 2025
1 check passed
@Dustymind Dustymind deleted the tigervnc-1.15.0-xserver21.1.17 branch June 18, 2025 11:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upgrade Topic/issue involves a package upgrade
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants