As a user, I want to attach an already uploaded package in a deb repo to multiple distributions
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start with the pulp deb repository content add command and trace how it creates repository content and publication references. Determine where a distribution can be selected, then verify that one uploaded package is referenced by the Packages metadata for trixie, bookworm, and bullseye without duplicating the pool file.
Written by the indexing model from the issue text.
Description
If my debian repository structure is as follows
.
├── dists
│ ├── bookworm
│ │ ├── InRelease
│ │ ├── main
│ │ │ ├── binary-amd64
│ │ │ │ ├── Packages
│ │ │ │ └── Packages.gz
│ │ │ ├── binary-arm64
│ │ │ │ ├── Packages
│ │ │ │ └── Packages.gz
│ │ │ └── source
│ │ │ ├── Packages
│ │ │ └── Packages.gz
│ │ ├── Release
│ │ └── Release.gpg
│ ├── bullseye
│ │ ├── InRelease
│ │ ├── main
│ │ │ ├── binary-amd64
│ │ │ │ ├── Packages
│ │ │ │ └── Packages.gz
│ │ │ ├── binary-arm64
│ │ │ │ ├── Packages
│ │ │ │ └── Packages.gz
│ │ │ └── source
│ │ │ ├── Packages
│ │ │ └── Packages.gz
│ │ ├── Release
│ │ └── Release.gpg
│ └── trixie
│ ├── InRelease
│ ├── main
│ │ ├── binary-amd64
│ │ │ ├── Packages
│ │ │ └── Packages.gz
│ │ ├── binary-arm64
│ │ │ ├── Packages
│ │ │ └── Packages.gz
│ │ └── source
│ │ ├── Packages
│ │ └── Packages.gz
│ ├── Release
│ └── Release.gpg
└── pool
└── main
└── f
└── foobar
├── foobar_1.0.0_amd64.deb
└── foobar_1.0.0_arm64.deb
I want to add the same foobar package to all three distributions - trixie, bookworm, and bullseye. So, the same file in pool, being referenced by Packages of all three distributions when a publication is created.
There is the pulp deb repository content add command which lets us add a package to a repository, but it can't specify a distribution.
- Dominant language
- Python
- Stars
- 5
- Forks
- 14
- Avg merge
- 22h 12m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No 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-cli-deb
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
pulp/pulp-cli-deb#272 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
pulp/pulp-cli-deb#243 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
pulp/pulp-cli-deb#232 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
pulp/pulp-cli-deb#157 ·
-
Feature Looking_for_Contributor
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
pulp/pulp-cli-deb#107 ·
All issues in pulp/pulp-cli-deb
Similar issues
-
Device Details tables: FS/SF columns contradict each other (nfet_01v8 Vt row, pfet_01v8 Idsat row)Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
google/skywater-pdk#450 ·
-
Drained trajectory arrays are overwritten when the sequence buffer is reusedPossibly taken @sylvesterkaczmarek claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
google-deepmind/bsuite#56 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
LearningCircuit/local-deep-research#7206 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
chingu-voyages/V62-tier3-team-33#285 ·
Maintainers usually reply within 1 day
-
Proxy drops log notifications from backends that don't send FastMCP's msg/extra dictPossibly taken @asasemahmed claimed this today. Openbug server
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day