rocky-linux / rocky-linux/documentation

Incus documentation is invalid / out of date

Open
#3,395 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
476
Forks
383
Avg merge
1d 14h
Merged PRs (30d)
20

Description

I'm looking through the instructions on docs.rockylinux.org and the provided copr is neil/incus. This repo does not contain incus for rocky 10 and is at least a year out of date for rocky 9.

I do a little more digging and discover that the linuxcontainers.org/incus documentation instructs you to install the neelc/incus copr.

The neelc/incus repository is labeled on copr.coprfedorainfracloud.org as being a fork of the original neil/incus.

The "official" documentation here assures me that Neil Hanlon is an official rocky infra co-lead, but then it actually requires a bait and switch to a different repository maintained by an account with an almost homopone name with no such provenance. It is claiming on the copr page that it's a fork of Neil's repo because the previous isn't compatible (?! A Rocky infra lead isn't maintaining it for rocky?)

While I don't think anything malicious is going on, I feel it's worth pointing out how incredibly suspect it looks from the outside.

I am not going to dig further into the why, but the docs need to have the incus section removed or assurances of it's support/compatibility need to be removed. Using Neil's credibility here is a bad idea for official documentation for something obviously not well maintained.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Incus section in the Rocky Linux documentation and inspect its neil/incus COPR reference and compatibility claims. Compare those instructions with the current Incus documentation reference to determine which statements are outdated. Done means the section no longer presents an outdated repository or unsupported compatibility claim.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.