pkworker: drop the usage of ProvidesEnum #7
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PkProvidesEnum was removed during the migration from 0.8.x to 0.9.x of packagekit this is what the porting document for backends has to say about PkProvidesEnum: * Remove the PkProvidesEnum parameter from pk_backend_what_provides() -- all provides should be done as if ANY is specified. so this should not be needed anymore (and in fact makes PackageKit worker never initialize and always skip to AptWorker) Signed-off-by: Bardia Moshiri <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PkProvidesEnum was removed during the migration from 0.8.x to 0.9.x of packagekit this is what the porting document for backends has to say about PkProvidesEnum:
so this should not be needed anymore (and in fact makes PackageKit worker never initialize and always skip to AptWorker)