macaroni-os / macaroni-os/mark-issues
[core-kit] sys-fs/lvm2 has broken IUSE sanlock
Open
Nobody has claimed this yet.
bug
core-kit
emerge failure
MARK
mark-testing
- Dominant language
- No language data
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
These are the packages that would be merged, in reverse order:
Calculating dependencies ... done!
emerge: there are no ebuilds to satisfy "sys-cluster/sanlock".
(dependency required by "sys-fs/lvm2-2.03.27::core-kit[sanlock,lvm]" [ebuild])
Do we really need sanlock? What is the status of the sanlock project?
FWIS it seems something related to Redhat/Ovirt stuff but it's not clear if it's a maintained project.
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.
Research direction
Start with the sys-fs/lvm2-2.03.27::core-kit ebuild and its sanlock IUSE and dependency settings. Reproduce the emerge failure for the [sanlock,lvm] configuration, then determine whether sanlock is still required. Done means the configuration no longer requests the unavailable sys-cluster/sanlock dependency, or the dependency is available and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100