pulp / pulp/pulp_deb

how can I skip package with bad checksum?(in Release file and in file checksum are not equal on remote_repo)

Open
#1,140 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Triage-Needed
Dominant language
Python
Stars
71
Forks
91
Avg merge
1d 19h
Merged PRs (30d)
22

Description

Hello
Problem : on remote repository package with bad checksum (not equal in Release file)

url="http://packages.linbit.com/public/"
distributions="proxmox-8"
architectures="amd64"
components="drbd-9"

When I run
pulp deb repository sync --name *** --remote ***
I recieve
'A file located at the url http://packages.linbit.com/public/dists/proxmox-8/drbd-9/pool/ktls-utils-dbgsym_0.10-2_amd64.deb failed validation due to checksum. Expected '10f931da9a6166ce09e2a6b0b56fd4710cc2a08f4747382099adbe75f32d9e7077a69d20cdb03f8990cc62f4b7d127b378e339d1455c042a7ed0f464c68d84a4', Actual 'fbf78d9e973d7d77a474d4b514ff56c8f62807179dd0389e8801638558452954fe8fa37d3e2a625b6401bbd5c83deaea3b484f542f3e4f65536ebac7fe937533''

How can I skip this package? It's really wrong checksum sha512sum in remote repo http://packages.linbit.com/public/ in one package only

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 with the pulp deb repository sync entry point and trace where the remote package checksum is validated. Determine whether the sync workflow exposes a way to exclude a single package, then verify the behavior against the reported ktls-utils-dbgsym_0.10-2_amd64.deb mismatch. Done means a documented, tested way to skip or otherwise handle this package without disabling checksum validation generally.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.