summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorColin Walters <walters@verbum.org>2013-09-19 22:26:03 -0400
committerColin Walters <walters@verbum.org>2013-09-19 22:26:43 -0400
commitd03b8bbad9f40024b994c03960758446c614f7a6 (patch)
tree96062dc9ad058d1703aad3ac82ea9cd648e44753
parentae68b8380fb83a9670aa8c05d2ad2c1bb0393092 (diff)
downloadostree-d03b8bbad9f40024b994c03960758446c614f7a6.tar.gz
deploy: Do a full system sync after writing bootloader config
This is just something I noticed on inspection; we should catch any changes to /boot in the sync(), even though theoretically gio should have done fdatasync().
-rw-r--r--src/libostree/ostree-sysroot-deploy.c10
1 files changed, 5 insertions, 5 deletions
diff --git a/src/libostree/ostree-sysroot-deploy.c b/src/libostree/ostree-sysroot-deploy.c
index 4639eadd..8a6fd4ea 100644
--- a/src/libostree/ostree-sysroot-deploy.c
+++ b/src/libostree/ostree-sysroot-deploy.c
@@ -1096,16 +1096,16 @@ ostree_sysroot_write_deployments (OstreeSysroot *self,
goto out;
}
- if (!full_system_sync (cancellable, error))
+ if (bootloader && !_ostree_bootloader_write_config (bootloader, new_bootversion,
+ cancellable, error))
{
- g_prefix_error (error, "Full sync: ");
+ g_prefix_error (error, "Bootloader write config: ");
goto out;
}
- if (bootloader && !_ostree_bootloader_write_config (bootloader, new_bootversion,
- cancellable, error))
+ if (!full_system_sync (cancellable, error))
{
- g_prefix_error (error, "Bootloader write config: ");
+ g_prefix_error (error, "Full sync: ");
goto out;
}