Determine the repo/PPA that a system package came from
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- debian, python, ubuntu
- Domain
- operating-systems
Research direction
The issue names no file, test, or entry point. Start by locating the Debian/Ubuntu system-package metadata handling, then determine how repository or PPA provenance can be obtained and represented. Done means the library can report the originating repository or PPA for an installed package, with coverage for the supported Debian-based systems.
Written by the indexing model from the issue text.
Description
For system installed packages for Debian or Ubuntu, it would be helpful to know which repo or PPA it came from.
- Dominant language
- Python
- Stars
- 17
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
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 aboutcode-org/debian-inspector
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
Add support for zstdOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
API documentationOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
aboutcode-org/debian-inspector#47 · 1 comment · 3 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
All issues in aboutcode-org/debian-inspector
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
GoogleCloudPlatform/professional-services-data-validator#1899 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mohanraj00/entelos#200 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
sweep
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
bketelsen/truenas-mcp#77 ·
Maintainers usually reply within 1 day
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
sandbox-quantum/switch#2163 ·
Maintainers usually reply within 1 day