Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add rpm-no-comps fixture #251

Merged
merged 1 commit into from
Mar 28, 2024
Merged

Add rpm-no-comps fixture #251

merged 1 commit into from
Mar 28, 2024

Conversation

chris1984
Copy link
Contributor

No description provided.

@chris1984
Copy link
Contributor Author

chris1984 commented Mar 26, 2024

@ggainey here is my attempt at the no-comps. Locally it looks correct.

Copy link
Collaborator

@ggainey ggainey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs to have a separate [noissue] line in the commit-message as well.

@@ -523,6 +526,10 @@ fixtures/rpm-zstd-metadata: fixtures
rpm/gen-fixtures.sh $@ rpm/assets
createrepo_c --general-compress-type=zstd --update $@

fixtures/rpm-no-comps: fixtures
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you make fixtures/rpm-no-comps using this, you end up with a repo whose repomd.xml points-to the comps.xml that you then remove. This will cause a sync of that repo to fail. You need to call rpm/genfixtures.sh on a directory that doesn't have a comps.xml to begin with.

Copy link
Contributor Author

@chris1984 chris1984 Mar 26, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That makes sense, the part about me breaking the repo with removing the comps.xml and the repomd.xml still pointing to it. The only 2 repos I found that didn't have a comps.xml was assets-modularity and assets-modular Would manually creating an assets directory from assets then updating the repomd.xml to not have any reference to comps.xml, remove the comps.xml then have the make file use that directory or is there a better way forward?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The general pattern is, in the build-stanza in the Makefile for your fixture, you cp -r from assets into your chosen dir-name, remove comps.xml, and then gen-fixture the resulting directory.

@chris1984
Copy link
Contributor Author

@ggainey I think I got it figured out, looks right locally based on your feedback. Updated my commit message to have [noissue] inside it as well on a new line. Let me know how this looks?

Copy link
Collaborator

@ggainey ggainey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@ggainey ggainey merged commit ebd9847 into pulp:master Mar 28, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants