Restore question about userspace upgrades #794

EvilOlaf · Aug 17, 2025

Why wasting time explaining over and over when this can be simply clarified in docs?

Documentation website preview will be available shortly:

Open WWW preview

Why wasting time explaining over and over when this can be simply clarified in docs?

coderabbitai · Aug 17, 2025

Warning

Rate limit exceeded

@EvilOlaf has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 21 minutes and 15 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between c4877c3 and d03f2c2.

📒 Files selected for processing (1)

docs/User-Guide_FAQ.md (1 hunks)

Walkthrough

Adds a new FAQ entry “Can I upgrade my userspace flavor?” to docs/User-Guide_FAQ.md. The entry explains that Armbian core component upgrades (kernel, firmware, boot loader) performed via apt are independent from userspace release upgrades, states Armbian does not provide or endorse a standardized userspace-upgrade path (e.g., Focal→Jammy, Bullseye→Bookworm), recommends using official Debian/Ubuntu procedures if attempted and freezing firmware via armbian-config, and warns that issues from userspace upgrades are not the responsibility of Armbian due to limited testing resources.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

FAQ - drop non relevant, reword, cleanup #781 — Previously reworked/removed userspace-upgrade guidance in the FAQ; directly overlaps with and affects the same FAQ content.

✨ Finishing Touches

🧪 Generate unit tests

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch EvilOlaf-patch-1

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

Visit our Status Page to check the current availability of CodeRabbit.
Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

coderabbitai

Actionable comments posted: 2

🧹 Nitpick comments (2)

docs/User-Guide_FAQ.md (2)

87-87: Optional: consider recommending full-upgrade for core component transitions.

If project policy allows, “apt full-upgrade” typically handles meta-package transitions (kernels) better than “upgrade.” If you prefer this guidance, adjust the sentence accordingly.

-Note: Upgrading Armbian core components (kernel, firmware, bootloader) and upgrading the chosen userspace are independent processes. The former is performed with `apt update && apt upgrade`.
+Note: Upgrading Armbian core components (kernel, firmware, bootloader) and upgrading the chosen userspace are independent processes. The former is performed with `apt update && apt full-upgrade`.

91-91: Optional: add links to official Debian/Ubuntu upgrade docs for convenience.

Direct links reduce ambiguity and support requests.

-You may attempt a userspace upgrade using the official Debian/Ubuntu methods. Before doing so, freeze Armbian firmware/kernel/bootloader packages via [armbian-config](https://docs.armbian.com/User-Guide_Armbian-Config/). Note: issues arising from such upgrades are out of scope for Armbian support.
+You may attempt a userspace upgrade using the official Debian/Ubuntu methods (e.g., Debian’s [DebianUpgrade](https://wiki.debian.org/DebianUpgrade) and Ubuntu’s [Upgrading](https://ubuntu.com/server/docs/upgrading)). Before doing so, freeze Armbian firmware/kernel/bootloader packages via [armbian-config](https://docs.armbian.com/User-Guide_Armbian-Config/). Note: issues arising from such upgrades are out of scope for Armbian support.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

MCP integration is disabled by default for public repositories
Jira integration is disabled by default for public repositories
Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 1c92745 and b44b090.

📒 Files selected for processing (1)

docs/User-Guide_FAQ.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/User-Guide_FAQ.md

[grammar] ~89-~89: Ensure spelling is correct
Context: ...son why we cannot is simply the lack of ressources in time and devices to test such upgrad...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

[grammar] ~91-~91: There might be a mistake here.
Context: ...ve other issues with an upgraded system.

(QB_NEW_EN)

🪛 markdownlint-cli2 (0.17.2)

docs/User-Guide_FAQ.md

85-85: Multiple top-level headings in the same document

(MD025, single-title, single-h1)