Project

Profile

Help

Story #1158

closed

As a user, I can force full/fresh publish of rpms and not do an incremental publish

Added by jluza over 8 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
2.9.0
Groomed:
No
Sprint Candidate:
Yes
Tags:
Easy Fix, Pulp 2
Sprint:
Sprint 1
Quarter:

Description

Pulp should have way how to prevent a second publish from being published as a fast-forward. For example when you need to fast way how to fix inconsistency between repodata/packages on disk and in database.

Suggested change:

https://github.com/release-engineering/pulp_rpm/commit/d16d6c831d71397f8a6b2b03ad1e8fad80120ef9


Related issues

Has duplicate RPM Support - Story #1098: Support a 'forced' metadata regenerationCLOSED - DUPLICATE

Actions
Blocks Pulp - Story #1724: Publish should be a no-op if no units and no settings have changed since the last successful publishCLOSED - CURRENTRELEASEipanova@redhat.com

Actions

Also available in: Atom PDF