When linking to dependencies, sometimes the "wrong" repository is chosen for a given package
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 50/100
Research direction
Start with the Arch package page for hyprpolkitagent and compare the links for qt6-base and qt6-declarative with the repositories those dependencies are available from. Trace how dependency repository links are selected, then verify that the resulting links use the expected repository for typical users or that the selection rule is clearly documented.
Written by the indexing model from the issue text.
Description
At the time of writing, under https://archlinux.org/packages/extra/x86_64/hyprpolkitagent/, there are two dependencies qt6-base and qt6-declarative that, instead of linking to extra, link to kde-unstable. If I understand Arch's packaging correctly, there is no canonical repository that can be chosen for every user since the repository for a dependency isn't chosen by the package itself. It's whatever repository the user has the dependency package installed from. But then this is pretty misleading for the vast majority of users. Should extra/core not be preferred?
- Dominant language
- JavaScript
- Stars
- 393
- Forks
- 157
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 7
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 archlinux/archweb
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
Upgrade to Django 6Open
Difficulty 4/5 3-5 days Newbie friendliness 50/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 42/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
All issues in archlinux/archweb
Similar issues
-
Complexity: Small P-Feature: Projects page ready for merge team role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100
bellingcat/toolkit#905 ·
-
self-care self-care:docs-build-time-investigator
Difficulty 2/5 Half a day Newbie friendliness 76/100
githubnext/gh-aw-cao#14191 ·
Maintainers usually reply within 1 day
-
effort:low impact:medium RAG status: auto-triaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
mastra-ai/mastra#25229 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sugarlabs/musicblocks#8984 ·
Maintainers usually reply within 1 day