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

'rpm-ostree upgrade' isn't reliably printing the result of the upgrade #396

Closed
miabbott opened this issue Jul 15, 2016 · 1 comment
Closed
Labels

Comments

@miabbott
Copy link
Member

Recent attempts to use rpm-ostree upgrade have not been reliably printing the Upgraded/Added/Removed status for the packages affected by the upgrade.

Since a lot has been changing in the internals, I'm guessing this regressed somewhere.

@cgwalters
Copy link
Member

I was playing with this:

diff --git a/src/app/rpmostree-builtin-upgrade.c b/src/app/rpmostree-builtin-upgrade.c
index 8c4f027..a86091c 100644
--- a/src/app/rpmostree-builtin-upgrade.c
+++ b/src/app/rpmostree-builtin-upgrade.c
@@ -129,14 +129,14 @@ rpmostree_builtin_upgrade (int             argc,
         goto out;
     }

-  new_default_deployment = rpmostree_os_dup_default_deployment (os_proxy);
-
   if (!rpmostree_transaction_get_response_sync (sysroot_proxy,
                                                 transaction_address,
                                                 cancellable,
                                                 error))
     goto out;

+  new_default_deployment = rpmostree_os_dup_default_deployment (os_proxy);
+
   if (opt_preview || opt_check)
     {
       g_autoptr(GVariant) result = NULL;

Which looks clearly right but that's not it...I think though we may need to drop into the mainloop to process signals.

@cgwalters cgwalters added the bug label Jul 16, 2016
cgwalters added a commit to cgwalters/rpm-ostree that referenced this issue Jul 17, 2016
First I noticed we needed to query the new default *after* the
transaction had run.  Then, I noticed the obvious embarassing logic
error.

Fixes: 3f1e7c85a18182669899f4065d23fec6ac0962c
Closes: coreos#396
cgwalters added a commit to cgwalters/rpm-ostree that referenced this issue Jul 17, 2016
First I noticed we needed to query the new default *after* the
transaction had run.  Then, I noticed the obvious embarassing logic
error.

Fixes: 3f1e7c85a18182669899f4065d23fec6ac0962c
Closes: coreos#396
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants