Update PURLDB with all ABCTK releases
@pombredanne is already working on this.
Since Mar 15, 2025.
Assessment
This issue has not been assessed yet.
Description
We need an automated process to update PURLDB whenever we release a new version of any AboutCode.org package - we should start with aboutcode-toolkit. If we have each release in PURLDB then you should be able to get that data for a Product in DejaCode with the Improve Packages from PURLDB Action.
The steps seem to be:
- Use the PURLDB API to get the current list of PURLs for aboutcode-toolkit and their data
- Identify missing or incorrect data in the existing PURL data and correct it
- Identify the missing PURLs and add them to PURLDB
- Figure out how to automatically populate the PURLDB for each new release of aboutcode-toolkit
This is a pilot for a process to:
- Clean up existing PURLDB data for all AboutCode projects
- Automate adding PURLDB data for each new release of an AboutCode project
The initial focus should be on AboutCode projects that are published to PyPI to keep this simple.
An open question is how to handle the different types of packages that we usually publish for aboutcode-toolkit (and most other AboutCode projects). Using v11.0.0 AboutCode Toolkit v11.0.0 as an example, we have 4 downloads:
- aboutcode_toolkit-11.0.0-py3-none-any.whl
- aboutcode_toolkit-11.0.0.tar.gz
- v11.0.0.zip (Source Code)
- v11.0.0.tar.gz (Source Code)
For patch releases like AboutCode Toolkit v11.0.1 and v11.0.2 (and many older versions) we only release the source packages.
Since each PURLDB record has one Download URL we will need some way to record the four different PURLs.
This seems to call for a qualifier so that the records will be unique. My guess is that we might want to treat the wheel as primary in the PyPI context and perhaps not use a qualifier for it.
- Dominant language
- Python
- Stars
- 100
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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/aboutcode-toolkit
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Enhance `about_resource` to reference multiple files.May be free again @chinyeungli claimed this 266 days ago, and no pull request is open. Open
aboutcode-org/aboutcode-toolkit#566 · 2 comments · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Create test file with a few hundred itemsMay be free again @DennisClark claimed this 1731 days ago, and no pull request is open. Open
aboutcode-org/aboutcode-toolkit#491 · 2 assignees ·
-
Clean up / Organize codeMay be free again @sahil-MK2 claimed this 1750 days ago, and no pull request is open. Open
aboutcode-org/aboutcode-toolkit#483 · 1 comment · 2 assignees ·
All issues in aboutcode-org/aboutcode-toolkit
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