Skip to content

feat: add Manjaro Stable package repositories - #108

Merged
ReenigneArcher merged 1 commit into
masterfrom
feat/manjaro-repositories
Nov 14, 2026
Merged

ReenigneArcher merged 1 commit into
masterfrom
feat/manjaro-repositories

Conversation

@ReenigneArcher

@ReenigneArcher ReenigneArcher commented Nov 14, 2026 •

Copy link
Copy Markdown
Member

Description

Arch-built Sunshine binaries can fail to start on Manjaro Stable when library versions diverge, as seen with glibc in #95 and now OpenSSL. Build stable and beta packages separately against Manjaro Stable, publishing them through lizardbyte-manjaro and lizardbyte-manjaro-beta.

  • Reuse the existing PKGBUILDs across four distribution/channel targets. Configure Manjaro Stable mirrors and keyrings, and compile the repo-builder against Manjaro's libraries.
  • Gate each release on package installation, library-resolution checks, and sunshine --version in a fresh matching container. Successful targets can publish independently of failed builds.
  • Preserve the existing Arch repository URLs and latest-release selection. Document Manjaro setup and explicit reinstallation when migrating an existing Arch package.

Screenshot

Issues Fixed or Closed

Related to #95, which is already closed. This PR addresses the similar OpenSSL/library compatibility problem on Manjaro Stable.

Roadmap Issues

Testing

Added fresh-container package installation, ldd checks for unresolved runtime libraries, and sunshine --version for each distribution/channel. These checks gate publishing and target the dependency mismatch described above.

  • actionlint v1.7.12: passed (workflow checks; ShellCheck/Pyflakes disabled).
  • YAML/configuration checks: passed for all four repository/release mappings, artifact routing, release selection, and migration commands.
  • git diff --check: passed.
  • Full Linux compilation and execution of the new runtime checks were not performed locally because Docker's daemon is unavailable. These checks run in PR CI.

Type of Change

  • feat: New feature (non-breaking change which adds functionality)
  • fix: Bug fix (non-breaking change which fixes an issue)
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
  • refactor: Code change that neither fixes a bug nor adds a feature
  • perf: Code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies
  • ci: Changes to CI configuration files and scripts
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

  • Code follows the style guidelines of this project
  • Code has been self-reviewed
  • Code has been commented, particularly in hard-to-understand areas
  • Code docstring/documentation-blocks for new or existing methods/components have been added or updated
  • Tests have been added or updated for new or modified functionality, including regression tests for bug fixes

AI Usage

See our AI usage policy.

  • AI tools were used while preparing this PR

@sonarqubecloud

Copy link
Copy Markdown

@ReenigneArcher
ReenigneArcher merged commit 95c242a into master Nov 14, 2026
16 checks passed
@ReenigneArcher
ReenigneArcher deleted the feat/manjaro-repositories branch November 14, 2026 12:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant