{"action":"created","issue":{"url":"https://api.github.com/repos/openSUSE/transactional-update/issues/16","repository_url":"https://api.github.com/repos/openSUSE/transactional-update","labels_url":"https://api.github.com/repos/openSUSE/transactional-update/issues/16/labels{/name}","comments_url":"https://api.github.com/repos/openSUSE/transactional-update/issues/16/comments","events_url":"https://api.github.com/repos/openSUSE/transactional-update/issues/16/events","html_url":"https://github.com/openSUSE/transactional-update/issues/16","id":363518597,"node_id":"MDU6SXNzdWUzNjM1MTg1OTc=","number":16,"title":"[Feature/usability] Allow multiple package installations or prompt user before discarding","user":{"login":"CySlider","id":136510,"node_id":"MDQ6VXNlcjEzNjUxMA==","avatar_url":"https://avatars1.githubusercontent.com/u/136510?v=4","gravatar_id":"","url":"https://api.github.com/users/CySlider","html_url":"https://github.com/CySlider","followers_url":"https://api.github.com/users/CySlider/followers","following_url":"https://api.github.com/users/CySlider/following{/other_user}","gists_url":"https://api.github.com/users/CySlider/gists{/gist_id}","starred_url":"https://api.github.com/users/CySlider/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/CySlider/subscriptions","organizations_url":"https://api.github.com/users/CySlider/orgs","repos_url":"https://api.github.com/users/CySlider/repos","events_url":"https://api.github.com/users/CySlider/events{/privacy}","received_events_url":"https://api.github.com/users/CySlider/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2018-09-25T10:52:27Z","updated_at":"2018-09-25T16:02:57Z","closed_at":null,"author_association":"NONE","body":"As a newbie to this I stumbled quite hard about the fact that you can only use one transactional-update pkg in <packagelist> command before rebooting.\r\n\r\nIntuitively I assumed that I could run multiple such modifications and they all would apply after the next reboot.\r\n\r\nSo I would suggest to either allow this or be more vocal about losing changes made before. I only spotted the relevant lines in the logs after being irritated why changes were still not there after reboot.\r\n\r\n    WARNING: Default snapshot differs from current snapshot.\r\n    WARNING: Any changes within the previous snapshot will be discarded!\r\n\r\nMaybe instead prompt the user like:\r\n    You have changes that require a reboot to be in effect. If you continue, those changes will be lost. Continue? [n/y]\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/openSUSE/transactional-update/issues/comments/424403343","html_url":"https://github.com/openSUSE/transactional-update/issues/16#issuecomment-424403343","issue_url":"https://api.github.com/repos/openSUSE/transactional-update/issues/16","id":424403343,"node_id":"MDEyOklzc3VlQ29tbWVudDQyNDQwMzM0Mw==","user":{"login":"laenion","id":2150415,"node_id":"MDQ6VXNlcjIxNTA0MTU=","avatar_url":"https://avatars1.githubusercontent.com/u/2150415?v=4","gravatar_id":"","url":"https://api.github.com/users/laenion","html_url":"https://github.com/laenion","followers_url":"https://api.github.com/users/laenion/followers","following_url":"https://api.github.com/users/laenion/following{/other_user}","gists_url":"https://api.github.com/users/laenion/gists{/gist_id}","starred_url":"https://api.github.com/users/laenion/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/laenion/subscriptions","organizations_url":"https://api.github.com/users/laenion/orgs","repos_url":"https://api.github.com/users/laenion/repos","events_url":"https://api.github.com/users/laenion/events{/privacy}","received_events_url":"https://api.github.com/users/laenion/received_events","type":"User","site_admin":false},"created_at":"2018-09-25T16:02:56Z","updated_at":"2018-09-25T16:02:56Z","author_association":"COLLABORATOR","body":"For now if you want to \"stack\" changes you can use `transactional-update shell` and execute any commands (e.g. multiple _zypper_ commands) there. That way you will only get one snapshot / transaction.\r\n\r\nI'd love to implement the ability to stack changes, especially as this is a popular feature request. However we rely on snapper for snapshot creation which will always use the currently mounted system as a base. To enable change stacking snapper would have to be extended to be able to create a snapshot of a different snapshot. I didn't have a look at the feasibility of that yet."}}
{"actor":{"display_login":"laenion"}}