Stop implying that one Ubuntu 3.11 unit lane validates the full Linux support surface Aman documents.\n\nSplit CI into an Ubuntu CPython 3.10/3.11/3.12 unit-package matrix, a portable install plus doctor smoke lane, and a packaging lane gated on both. Add a reproducible ci_portable_smoke.sh helper with fake systemctl coverage, and force the installer onto /usr/bin/python3 so the smoke path uses the distro-provided GI and X11 Python packages it is meant to validate.\n\nUpdate the README, release/distribution docs, and Debian metadata to distinguish the automated Ubuntu CI floor from broader manual GA signoff families, and add the missing AppIndicator introspection package to the Ubuntu/Debian dependency lists.\n\nValidate with python3 -m unittest discover -s tests -p 'test_*.py', python3 -m py_compile src/*.py tests/*.py, and bash -n scripts/ci_portable_smoke.sh. The full xvfb-backed smoke could not be run locally in this sandbox because xvfb-run is unavailable.
2.2 KiB
2.2 KiB
Aman 1.0.0
This is the first GA-targeted X11 release for Aman.
- Canonical release page:
https://git.thaloco.com/thaloco/aman/releases/tag/v1.0.0 - Canonical release index:
https://git.thaloco.com/thaloco/aman/releases - Support and issue reporting:
thales@thalesmaciel.com
Supported environment
- X11 desktop sessions only
systemd --userfor supported daily use- System CPython
3.10,3.11, or3.12for the portable installer - Runtime dependencies installed from the distro package manager
- Automated validation floor: Ubuntu CI on CPython
3.10,3.11, and3.12for unit/package coverage, plus portable install andaman doctorsmoke with Ubuntu systempython3 - Manual GA signoff families: Debian/Ubuntu, Arch, Fedora, openSUSE
Artifacts
The release page should publish:
aman-x11-linux-1.0.0.tar.gzaman-x11-linux-1.0.0.tar.gz.sha256SHA256SUMS- wheel artifact from
dist/*.whl - Debian package from
dist/*.deb - Arch package inputs from
dist/arch/PKGBUILDanddist/arch/*.tar.gz
Install, update, and uninstall
- Install: download the portable bundle and checksum from the release page,
verify the checksum, extract the bundle, then run
./install.sh - Update: extract the newer bundle and run its
./install.sh - Uninstall: run
~/.local/share/aman/current/uninstall.sh - Purge uninstall: run
~/.local/share/aman/current/uninstall.sh --purge
The full end-user lifecycle is documented in
docs/portable-install.md.
Recovery path
If the supported path fails, use:
aman doctor --config ~/.config/aman/config.jsonaman self-check --config ~/.config/aman/config.jsonjournalctl --user -u amanaman run --config ~/.config/aman/config.json --verbose
Reference diagnostics and failure IDs live in
docs/runtime-recovery.md.
Support
Email thales@thalesmaciel.com with:
- distro and version
- X11 confirmation
- install channel and Aman version
aman doctoroutputaman self-checkoutput- relevant
journalctl --user -u amanlines
Non-goals
- Wayland support
- Flatpak or snap as the canonical GA path
- Native-package parity across every Linux distro