We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Version 0.13
Describe the bug Right now if I have the following collection versions:
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.
foo.a
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.
foo.bar:1.0.0
foo.a:1.0.0
Additional context Galaxy NG issue: https://issues.redhat.com/browse/AAH-932
The text was updated successfully, but these errors were encountered:
Allow deleting collection versions when another version of the collec…
e983501
…tion satisfies requirements. fixes: pulp#933
45a8ed5
c1bea33
…tion satisfies requirements. fixes: #933
4f400eb
…tion satisfies requirements. fixes: #933 (cherry picked from commit c1bea33)
d4c2ecd
Successfully merging a pull request may close this issue.
Version
0.13
Describe the bug
Right now if I have the following collection versions:
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 forfoo.a:1.0.0
is still satisfied.Additional context
Galaxy NG issue: https://issues.redhat.com/browse/AAH-932
The text was updated successfully, but these errors were encountered: