You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used transactional-update shell to mess around with the system and then later decided that I did not want the changes. The following seemed straight forward:
...
Please reboot your machine to activate the changes and avoid data loss.
New default snapshot is #291 (/.snapshots/291/snapshot).
transactional-update finished
dhcp144:~ # tukit abort
2021-04-29 09:21:16 tukit 3.3.0 started
2021-04-29 09:21:16 Options: abort
ERROR: basic_string::_M_construct null not valid
dhcp144:~ # tukit abort 291
2021-04-29 09:21:24 tukit 3.3.0 started
2021-04-29 09:21:24 Options: abort 291
ERROR: Snapshot 291 is not an open transaction.
would be nice if that just worked :-)
Had to use rollback which I feel is not intuitive as the new snapshot was never active.
Related to that would be nice if tukit would just report the current status when called wthout arguments (ie open transaction, pending snapshot etc).
The text was updated successfully, but these errors were encountered:
tukit abort is intended to be used for manual transaction handling, what you want is transactional-update rollback. However as more functionality - and especially snapshot management - will move into tukit I'll see what I can do :-)
I used transactional-update shell to mess around with the system and then later decided that I did not want the changes. The following seemed straight forward:
would be nice if that just worked :-)
Had to use rollback which I feel is not intuitive as the new snapshot was never active.
Related to that would be nice if tukit would just report the current status when called wthout arguments (ie open transaction, pending snapshot etc).
The text was updated successfully, but these errors were encountered: