Skip to content

Port Roundup appliance to TurnKey 19 - #18

Open
lirazsiri wants to merge 6 commits into
masterfrom
wish/roundup-v19-trixie
Open

Port Roundup appliance to TurnKey 19#18
lirazsiri wants to merge 6 commits into
masterfrom
wish/roundup-v19-trixie

Conversation

@lirazsiri

Copy link
Copy Markdown
Member

Summary

  • port the Roundup appliance to TurnKey 19 on Debian Trixie
  • update application installation, configuration, and runtime integration for the supported Trixie stack
  • add executable v19 smoke coverage and retain the accepted migration evidence

Validation

  • passed the configured Trixie root build in the Docker-based TKLDev 19 harness
  • passed noninteractive firstboot and the primary application workflow
  • passed dependency provenance and updater checks recorded in docs/v19.0-testing.md
  • git diff --check origin/master...HEAD

Move the appliance to Debian 13 and Roundup 2.6.0 while keeping Debian packages authoritative for Python, MariaDB integration, timezone data, Apache, and service dependencies. Pin and verify the official PyPI source distribution because Trixie has no Roundup package.

Replace the obsolete parallel installer with a supervised updater for the deployed virtual environment, and use Roundup itself to set the firstboot administrator password. Cover normal boot, administrator web login, issue create/read/update persistence, management services, signed update paths, and a disposable 2.5.0 to 2.6.0 data-preserving upgrade.
Roundup item pages include more than one CSRF-protected form. Restrict the focused acceptance helper to the first matching input and its value so the test submits the actual issue form token instead of the following action value.

Verified the unchanged login and web issue create, read, update, and MariaDB readback flow through an equivalent Apache mod_wsgi Trixie container.
The focused test runs with pipefail, so grep -q could close the Apache module pipeline after matching WSGI and surface apache2ctl SIGPIPE as a failure. Consume the complete module list while retaining the same exact WSGI assertion.

Verified the consuming module check in the disposable Trixie Apache and mod_wsgi runtime.
Three exact runs exited silently in the early Roundup identity block because the focused test had no failing-command context. Add a minimal ERR trap that prints only the source line, status, and command before normal cleanup.

This changes test observability only. It adds no retry, harness behavior, or product runtime behavior and preserves the final fix loop for a concrete correction.
The deployed virtual environment intentionally exposes Debian system packages. A global pip check therefore evaluates unrelated Debian Python metadata and can fail even when Roundup and its selected integration modules are complete.

Remove only that invalid global assertion. The focused test continues to import Roundup WSGI, MySQLdb and pytz and verifies that both integration modules are owned by Debian packages.
Replace the pending evidence placeholder after the clean candidate completed the required appliance validation. The report now ties the documented main-flow result to its exact source commit, harness revision, archive digest, run identifier, installed versions, and retained report path.

This commit changes documentation only. Verification: run 20260824t115118z-474-23163 passed build, import, normal runtime readiness, inithooks, and focused runtime tests.
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