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

Allow deleting collection versions when another version of the collection satisfies requirements #933

Closed
newswangerd opened this issue Apr 29, 2022 · 0 comments · Fixed by #934

Comments

@newswangerd
Copy link
Contributor

Version
0.13

Describe the bug
Right now if I have the following collection versions:

  • foo.bar:1.0.0
  • foo.bar:1.0.1
  • foo.a:1.0.0 with dependencies on foo.bar=*

I can't delete foo.bar 1.0.0 or 1.0.1 even though deleting one or the other will still allow for foo.a to satisfy it's dependency chain.

Expected behavior
I should be able to delete foo.bar:1.0.0 as long as the dependency chain for foo.a:1.0.0 is still satisfied.

Additional context
Galaxy NG issue: https://issues.redhat.com/browse/AAH-932

newswangerd added a commit to newswangerd/pulp_ansible that referenced this issue Apr 29, 2022
newswangerd added a commit to newswangerd/pulp_ansible that referenced this issue May 12, 2022
mdellweg pushed a commit that referenced this issue May 12, 2022
patchback bot pushed a commit that referenced this issue Jun 2, 2022
…tion satisfies requirements.

fixes: #933
(cherry picked from commit c1bea33)
fao89 pushed a commit that referenced this issue Jun 3, 2022
…tion satisfies requirements.

fixes: #933
(cherry picked from commit c1bea33)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant