Issue #4268
closed
Publishing a repo in-place multiple times creates multiple modules.yaml archives
Description
Even if nothing has changed in the repository, publishing an RPM repository several times will result in multiple modules.yaml.gz archives, even if the repository has no modules data (the modules.tar.gz archives are all empty), and each has different hashes.
Files
- Triaged changed from No to Yes
- Sprint set to Sprint 46
- Subject changed from Publishing a repo in-place creates multiple modules.yaml archives to Publishing a repo in-place multiple times creates multiple modules.yaml archives
- Status changed from NEW to ASSIGNED
- Assignee set to CodeHeeler
- Description updated (diff)
- Related to Issue #4252: modules.yaml file is generated on repository with no modularity information added
- Status changed from ASSIGNED to NEW
- Assignee deleted (
CodeHeeler)
- Sprint changed from Sprint 46 to Sprint 47
- Status changed from NEW to ASSIGNED
- Assignee set to dalley
- Status changed from ASSIGNED to POST
- Status changed from POST to CLOSED - NOTABUG
I believe this is actually not an issue. Only one file is listed in repomd.xml. The OldRepoData cleanup step should take care of this just like everything else.
Also available in: Atom
PDF