Add Debian, Ubuntu and Mint candidate profiles with scoped systemd 255 credentials
This commit is contained in:
FrameBridge compatibility build committed
1 parent
b23819fff1
commit
a48a20c936
28 files changed
+2527
-274
No files matched your search
@@ -1,6 +1,6 @@
|
||||
# FrameBridge — command guide
|
||||
|
||||
Version: 0.3.1 | Guide schema: 1
|
||||
Version: 0.3.2~compat.20261027.1 | Guide schema: 1
|
||||
|
||||
This reference is generated from the shared CLI/MCP guide. Use the matching installed version.
|
||||
|
||||
@@ -33,16 +33,16 @@ fb --json status
|
||||
|
||||
### Install and connect
|
||||
|
||||
On a supported Debian system, install the downloaded package with the package manager. Normal first connection does not require a separate setup, doctor or start sequence. Run connect in a normal interactive terminal. Advanced setup is optional for selecting central/node roles and public settings.
|
||||
Install the .deb built for your exact Debian 13, Ubuntu 24.04/26.04, Linux Mint 22.x or LMDE 7 amd64 profile. These compatibility candidates still require installation and lifecycle validation on each target. Select the artifact from the matching profile folder and keep the distribution system Python. Normal first connection does not require a separate setup, doctor or start sequence. Run connect in a normal interactive terminal; advanced setup is optional for central/node roles and public settings.
|
||||
|
||||
~~~sh
|
||||
sudo apt install ./FrameBridge-0.3.1.deb
|
||||
sudo apt install ./framebridge-expanded_0.3.2~compat.20261027.1_amd64.deb
|
||||
fb connect
|
||||
~~~
|
||||
|
||||
### Updating and removal
|
||||
|
||||
Install an official update through the normal package manager. Normal package removal stops package-owned managed processes and retains the profile and saved encrypted connection material for deliberate reuse; it is not a credential-forgetting operation. Use the separately documented explicit forget action first if that is your intended outcome. Do not assume purge erases user-profile data.
|
||||
Install an official update through the normal package manager when that update has been published. Normal removal stops package-owned managed processes and can retain the user profile and encrypted connection material; it is not a credential-forgetting operation. On systemd 255, package removal also revokes the administrative boot-credential grant. After reinstalling, run fb connect interactively to provision that grant again; retained files alone do not restore startup. Use the explicit credentials forget action first when that is your intended outcome. Do not assume purge erases user-profile data.
|
||||
|
||||
~~~sh
|
||||
sudo dpkg --remove framebridge-original-expanded
|
||||
@@ -303,7 +303,7 @@ A CLI tty transcript describes a terminal and explicitly does not claim authenti
|
||||
|
||||
### Automatic graphical discovery
|
||||
|
||||
The installer and control console stay text interfaces in both TTY and a desktop terminal. Compatible graphical CUA is discovered automatically; availability depends on the actual display/session and permissions. A loaded module is not proof that real pixel capture or input succeeded. New profiles use adaptive auto mode: without a verified active X11 session the runtime provides FBEXEC, FBTERM and CUA-TTY in text mode, without requiring a graphical login or automatically creating a private desktop. Explicit virtual-desktop settings remain advanced options and are labelled separately from physical-screen evidence.
|
||||
The installer and control console stay text interfaces in both TTY and a desktop terminal. Compatible graphical CUA is discovered automatically; availability depends on the actual display/session and permissions. A loaded module is not proof that real pixel capture or input succeeded. New profiles use adaptive auto mode: without a verified active X11 session the runtime provides FBEXEC, FBTERM and CUA-TTY in text mode, without requiring a graphical login or automatically creating a private desktop. Explicit virtual-desktop settings remain advanced options and are labelled separately from physical-screen evidence. Physical-screen capture and input currently require the supported active X11 session. Native Wayland control is not validated; showing an XWayland window does not establish full-desktop capture or input.
|
||||
|
||||
~~~sh
|
||||
fb status
|
||||
@@ -340,7 +340,7 @@ fb status boot
|
||||
|
||||
### Doctor
|
||||
|
||||
doctor diagnoses prerequisites and reports findings with suggested next steps. It is not an implicit repair, and it is not a substitute for checking actual live connection state. Inspect the diagnosis and relevant private application logs before considering configuration changes.
|
||||
doctor diagnoses prerequisites and reports findings with suggested next steps. It is not an implicit repair, and it is not a substitute for checking actual live connection state. Inspect the diagnosis and relevant private application logs before considering configuration changes. Candidate eligibility checks the exact OS release, amd64 architecture, package profile and CPython ABI before starting native components. Debian 13/LMDE 7 use cp313, Ubuntu 24.04/Mint 22.x use cp312, and Ubuntu 26.04 uses cp314. A matching profile does not establish a tested installation; never repair an ABI mismatch by replacing system Python or weakening package dependencies.
|
||||
|
||||
~~~sh
|
||||
fb doctor
|
||||
|
||||
@@ -0,0 +1,80 @@
|
||||
# Debian, Ubuntu and Linux Mint compatibility candidate
|
||||
|
||||
This development candidate is based on signed 0.3.1 source commit
|
||||
b23819fff1500cd43bb7c44dc9d866e3fb701672.
|
||||
Candidate version: 0.3.2~compat.20261027.1.
|
||||
|
||||
## Scope
|
||||
|
||||
Only Debian, Ubuntu and Linux Mint are in this candidate's support plan.
|
||||
Initial architecture: amd64/x86_64.
|
||||
|
||||
| Profile | Native interpreter ABI |
|
||||
| --- | --- |
|
||||
| Debian 13 | cp313 |
|
||||
| Ubuntu 24.04 | cp312 |
|
||||
| Mint 22.x (Ubuntu Noble base) | cp312 |
|
||||
| Ubuntu 26.04 | cp314 |
|
||||
| LMDE 7 (Debian Trixie base) | cp313 |
|
||||
|
||||
A build profile is not installation evidence. Results must distinguish static
|
||||
and unit checks, interpreter imports, disposable OS installation, and a pilot
|
||||
on a real machine. Mint and LMDE are separate targets.
|
||||
|
||||
## Changes and boundaries
|
||||
|
||||
Platform preflight uses explicit profiles and an installed manifest tied to the
|
||||
Python ABI and native modules. Build checks reject wrong native ABI, CPU,
|
||||
dependency versions and unsupported libc requirements.
|
||||
|
||||
Python 3.12/3.14 vendors preserve the pinned dependency versions. Only three
|
||||
CPython-specific native distributions are replaced with matching official wheels.
|
||||
Record their URLs and SHA-256 digests. The abi3 cryptography build is retained
|
||||
when its requirements are satisfied.
|
||||
|
||||
The system Python stays intact. Standalone interpreters in the isolated build
|
||||
workspace are build/test tools, not payload runtimes.
|
||||
|
||||
Protected user-service credentials retain the systemd >=256 route. Systemd 255
|
||||
support requires a separately installed, narrowly scoped helper and explicit
|
||||
owner provisioning. Missing backend must fail closed. Read its documentation
|
||||
and tests before installing or provisioning it.
|
||||
|
||||
Physical desktop capture/control remains X11 based. A functioning CLI, virtual
|
||||
display or Xwayland window does not establish physical Wayland desktop support.
|
||||
ARM, Alpine and other distribution families are outside this candidate scope.
|
||||
|
||||
## Build and evidence
|
||||
|
||||
From the source root, use an explicit target and ABI-matched vendor:
|
||||
|
||||
python3 source/packaging/build_expanded.py --target mint22-amd64-py312 --vendor-dir /absolute/path/to/vendor-cp312 --version '0.3.2~compat.20261027.1'
|
||||
|
||||
Use the Debian/Ubuntu/LMDE target IDs documented by the builder. Output files and
|
||||
manifests are separated by target. Candidate files need their own checksums and
|
||||
must not reuse the signed 0.3.1 download path or signatures.
|
||||
|
||||
Native wheel provenance and matching source must accompany the candidate.
|
||||
Existing license/source notices refer to the same upstream versions; preserve
|
||||
the new wheel identities with the new build evidence.
|
||||
|
||||
## Pilot on existing machines
|
||||
|
||||
Order: disposable Debian and Ubuntu 24.04 VMs, GERAMEG (Debian 13), then ASUS
|
||||
(Mint 22.3). Exclude GERANAS from this initial pilot: it is the central router
|
||||
and its 160 GB RAID contains a degraded member.
|
||||
|
||||
The original services observed today run outside this published package.
|
||||
Publishing the 0.3.1 website did not install its .deb on these hosts. GERAMEG
|
||||
also has older Alpha packages. Check package ownership, file paths, maintainer
|
||||
scripts, dependency transactions, ports and state before installation.
|
||||
|
||||
A production pilot needs separate owner authorization after concrete results:
|
||||
|
||||
- Review exact candidate checksum and dependency simulation.
|
||||
- Confirm a recoverable backup for every existing path it will change.
|
||||
- Retain an independent management route and the original service.
|
||||
- Install before provisioning a new connection or replacing an existing role.
|
||||
- Explain and authorize permission, udev, sudoers or service changes.
|
||||
- Prove rollback/removal in a disposable machine, including credential cleanup
|
||||
and preservation of unrelated owner files.
|
||||
Reference in new issue
Block a user