Feedback for "Install"
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- fedora
- Domain
- documentation
Research direction
Open the Terra docs at the “Bazzite and Aurora” section and compare it with the “Fedora Atomic and Derivatives” steps described in the issue. Add a verification step and a pointer to the repository-file and terra-release instructions when Terra is absent, then confirm the rendered documentation accurately reflects the suggested recovery path.
Written by the indexing model from the issue text.
Description
Hi! Quick docs improvement request based on a fresh Bazzite install (GNOME/Wayland, Fedora 43 base).
The Terra docs at https://developer.fyralabs.com/terra/installing#bazzite-and-aurora state:
Bazzite and Aurora come with Terra out of the box, simply rpm-ostree away!
but on my system the Terra repo was not enabled initially. rpm-ostree install espanso-wayland failed with “Packages not found”, and the enabled rpm-md repos listed were only fedora, updates, etc.
Running the “Fedora Atomic and Derivatives” steps from the Terra docs fixed it immediately:
curl -fsSL https://github.com/terrapkg/subatomic-repos/raw/main/terra.repo | pkexec tee /etc/yum.repos.d/terra.repo
sudo rpm-ostree install terra-release
After that, I could find and install the package I was looking for.
Suggestion:
In the “Bazzite and Aurora” section, add a one-line verification step (e.g., confirm terra appears in rpm-ostree enabled repos / confirm rpm-ostree search terra-release returns results), and if not present, point users to the Atomic repo-file + terra-release instructions.
This would prevent a lot of confusion for new users unfamiliar with the way this works, because the current text reads as unconditional!
Thanks!
- Dominant language
- MDX
- Stars
- 14
- Forks
- 19
- Avg merge
- 7d 12h
- Merged PRs (30d)
- 9
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FyraLabs/devdocs
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
documentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
documentation enhancement
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Feedback for “FAQ” Open
Difficulty 4/5 3-5 days Newbie friendliness 30/100
All issues in FyraLabs/devdocs
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100