Repo versions not created via sync should not be verbatim published
Open
Nobody has claimed this yet.
.feature
- Dominant language
- Python
- Stars
- 71
- Forks
- 91
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 22
Description
The verbatim publisher should do some sanity checking, and refuse to run for repo versions that cannot be meaningfully verbatim published. Right now this is possible (will run successfully), but won't create a publication with metadata (i.e. a publication that cannot be consumed by an APT client).
Contributor 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.
Research direction
Start at the verbatim publisher entry point and trace how repository versions reach it, especially versions not created through sync. Identify the existing publication checks and add coverage showing that unsupported versions are refused rather than published without metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100