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
PackageGroup related_packages removal #1745
PackageGroup related_packages removal #1745
Conversation
|
Attached issue: https://pulp.plan.io/issues/6410 |
696abd6
to
3d9f248
Compare
600e293
to
bfd7e48
Compare
bfd7e48
to
5b02a0a
Compare
|
This is an easy review since it's just removals :) LGTM While it's still fresh in your mind, it would be good to start writing down any thoughts you have on how to implement copy in the issue [0], or even start a branch to prototype and work on implementing it so that if anything else needs to be done to make it work, we can know early. |
|
@pavelpicka After thinking about it more I do think we should tie this work in together with https://pulp.plan.io/issues/6316 and merge it all together (maybe in this PR). That way we can know for certain that there are no issues with the strategy before we push this migration to users. If you would like to work on this I would definitely be available to help and answer questions. It would be good to have someone else with experience working on the copy code :) |
5b02a0a
to
2470c69
Compare
|
Why commit says |
2470c69
to
e1acda3
Compare
|
It is not. Updated to 'closes'. |
PackageGroup doesn't specify package version so any package can be used with list of packages already present in PackageGroup. Also removed relations to PackageGroup and each other for PackageCategory and PackageEnvironment. [nocoverage] closes: #6410 https://pulp.plan.io/issues/6410
e1acda3
to
0dc1e13
Compare
PackageGroup doesn't specify package version so any can be used with list
of packages already present in PackageGroup.
[nocoverage]
closes: #6410
https://pulp.plan.io/issues/6410