Any plans to support replication for deb type remotes/repositories/distributions ?
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by reading the replication implementation for RPM objects and the corresponding Debian remotes, repositories, and distributions; the issue names no files or tests. Identify which Debian object types fail to replicate and compare their behavior with RPM replication. Done means Debian objects can be replicated from a master to downstream servers in the same way as RPM objects.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Currently planning to use replication in order to distribute content across multiple downstream servers from single point. This is based on pulp replication, created the upstream object on the downstream to replicate from the master with rpm and deb remotes/repositories/distributions. RPM part worked like a charm, but deb no.
Describe the solution you'd like
I'd love deb type objects being replicated the same way as rpm one.
- Dominant language
- Python
- Stars
- 73
- Forks
- 94
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the 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 pulp/pulp_deb
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Triage-Needed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
Triage-Needed
Difficulty 5/5 Over a week Newbie friendliness 35/100
pulp/pulp_deb#1515 · 2 comments ·
Maintainers usually reply within 2 days
-
.bugfix
Difficulty 3/5 1-2 days Newbie friendliness 55/100
pulp/pulp_deb#1507 · 11 comments ·
Maintainers usually reply within 2 days
-
Remote not signedOpenTriage-Needed
Difficulty 3/5 1-2 days Newbie friendliness 58/100
pulp/pulp_deb#1498 · 6 comments · 1 reaction ·
Maintainers usually reply within 2 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Treat corrupt-shape state files as missing in `load_state`Possibly taken @Qrytics claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
OvertureMaps/overturemaps-py#175 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
awslabs/visual-asset-management-system#1278 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aws-samples/sample-per-model-bedrock#835 ·
Maintainers usually reply within 1 day