pulp / pulp/pulp_deb

Synchronizing content with Teleport provider results in 0 deb packages

Open
#1,233 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

.bugfix
Dominant language
Python
Stars
71
Forks
91
Avg merge
1d 19h
Merged PRs (30d)
22

Description

Version
rubygem-pulp_deb_client-3.3.1-1.el9.noarch
katello-repos-4.15.0-1.el9.noarch
katello-certs-tools-2.10.0-1.el9.noarch
foreman-installer-katello-3.13.0-1.el9.noarch
katello-selinux-5.0.2-1.el9.noarch
katello-common-4.15.0-1.el9.noarch
rubygem-katello-4.15.0-1.el9.noarch
katello-4.15.0-1.el9.noarch
katello-client-bootstrap-1.7.9-2.el9.noarch
rubygem-hammer_cli_katello-1.15.0-0.1.pre.main.20241104082525gitd2c7a35.el9.noarch

Describe the bug
Synchronizing from Teleport repository results in 0 debian packages in Pulp.

To Reproduce
Create a repository.
Set upstream to https://apt.releases.teleport.dev/debian
Set release to bookworm
Either leave component empty, or set it to stable/v17.
Sync.

Expected behavior
I'd expect packages to be synced.
What I see is 0 debian packages.

Additional context
https://apt.releases.teleport.dev/debian/dists/bookworm/InRelease

I can see an InRelease & Release file here. However, most apt repositories allow directory listing, but Teleport's doesn't.
I suspect Pulp requires directory listing, but one of our other sync scripts (https://github.com/apt-mirror/apt-mirror) doesn't require this and syncs Teleport just fine.

I'd expect Pulp to fetch a Release/Package file and grab the files from there, without needing directory listing.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the sync against https://apt.releases.teleport.dev/debian with the bookworm release and the stated component settings. Trace how the Debian sync handles the InRelease and Release metadata when directory listing is unavailable. Done means the repository imports the expected Debian packages without requiring directory listing.

Written by the indexing model from the issue text.

Assessment

Tech stack
debian, python
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.