-
Notifications
You must be signed in to change notification settings - Fork 418
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
Transaction Store/Replay #1630
Transaction Store/Replay #1630
Conversation
This pull request introduces 2 alerts and fixes 1 when merging 8d26f50 into 126d861 - view on LGTM.com new alerts:
fixed alerts:
|
This pull request introduces 2 alerts and fixes 1 when merging 251ba6d into 126d861 - view on LGTM.com new alerts:
fixed alerts:
|
I've added all the check mentioned earlier: Check for when a package wasn't found, check for extra packages in transaction and check for already installed versions. I've also implemented storing groups in the JSON (though I'm not entirely sure of the format), but I don't know how to implement installing the groups. An updated TODO list:
|
The overall approach looks good to me, just couple notes about the store command and the stored json file: I'd add |
This pull request introduces 2 alerts and fixes 1 when merging 0caba25 into f283605 - view on LGTM.com new alerts:
fixed alerts:
|
@dmach I've addressed most of your points except the I've also attempted to make the |
This pull request introduces 2 alerts and fixes 1 when merging 85dd536 into f283605 - view on LGTM.com new alerts:
fixed alerts:
|
I am sorry but I am unable to build PR.
|
Sorry about that, I've fixed it. Thanks for the review! |
This pull request introduces 2 alerts and fixes 1 when merging deb9e64 into f283605 - view on LGTM.com new alerts:
fixed alerts:
|
This pull request introduces 2 alerts and fixes 1 when merging e5f5de2 into f283605 - view on LGTM.com new alerts:
fixed alerts:
|
This pull request introduces 1 alert and fixes 3 when merging 9519898 into f283605 - view on LGTM.com new alerts:
fixed alerts:
|
This pull request introduces 1 alert and fixes 3 when merging 87b1557 into f283605 - view on LGTM.com new alerts:
fixed alerts:
|
I've pushed a final version for this PR. I've left the accumulation of errors throughout the file (as opposed to printing the first error only) in a separate commit, because I'm not entirely happy with it, so I wanted to single it out for the review. I'll squash it with the other commit if there are no issues with it during the review. List of things remaining to be implemented at a later stage:
|
This pull request introduces 1 alert and fixes 1 when merging 29d2147 into 829fa0a - view on LGTM.com new alerts:
fixed alerts:
|
This pull request introduces 1 alert and fixes 1 when merging 223e4eb into 5d0e0d3 - view on LGTM.com new alerts:
fixed alerts:
|
This pull request introduces 1 alert and fixes 1 when merging a623aeb into 5d0e0d3 - view on LGTM.com new alerts:
fixed alerts:
|
I am really sorry, but I am unable to build it:
|
This pull request introduces 1 alert and fixes 1 when merging cca293d into 5d0e0d3 - view on LGTM.com new alerts:
fixed alerts:
|
It's because of this commit: a6d41db Where I change the name of the argument to unify it with the |
Plus some imports cleanup.
Call it in run() and store the results locally. Store the configuration it uses in the class instance and unify naming of some variables.
This pull request introduces 1 alert and fixes 1 when merging 2b5b130 into 5d0e0d3 - view on LGTM.com new alerts:
fixed alerts:
|
In this case I would recommend to keep the original name of the argument. The benefit of the change is minimal, but consequences could be huge. Who knows? |
…stall Converts the pkg_types only if they're not already integers. Adds documentation for the argument.
Raising ValueError in _group_install() was a mistake, the error that is expected is CompsError. It will also get caught in install_or_skip(), which is an unfortunately unreliable interface, but one that we're stuck with for backwards compatibility. Raises a CompsError in the same situation in _environment_install() as well.
Proxies the underlying RPMItem getNEVRA().
The enum values for PackageType are different between libcomps and libdnf, translate the value when storing the libcomps data into a Swdb transaction.
Fixed. Builds for me now. |
This pull request introduces 1 alert and fixes 1 when merging 99b1f20 into 5d0e0d3 - view on LGTM.com new alerts:
fixed alerts:
|
I see that two tests are failing:
@lukash Please could you fix it? |
Fixed. The tests now depend on |
All tests passed, thank you very much for a contribution. |
The basics work, there are TODOs scattered through the code.
What remains to be done:
I'm calling the modules etc. in various places
transaction_sr
ortransaction-sr
, though I'm not too happy with the name, would change it to a better one but can't think of any.Requires this libdnf PR: rpm-software-management/libdnf#972
Tests: rpm-software-management/ci-dnf-stack#845