Thank you for the reply.
My idea is to update, then shutdown. There is probably lots of technical hurdles to this,
I wouldn't be much help there, but its the only way i see coming out the other side
updated and actually shut down.
On December 23, 2016 5:16:56 PM GMT+03:00, Matthew Miller <mattdm(a)fedoraproject.org>
On Fri, Dec 23, 2016 at 08:54:35AM +0300, Allan Mwenda wrote:
> So I posted my first bug on bugzilla, not sure if i did it exactly
> but i gave it my best shot. Still learning, cheers.
This is a good report, but the issue you raise (LUKS passphrase needed
for the reboot in offline updates) is a big and difficult problem that,
frankly, I haven't heard any great ideas for solving. The updates are a
applied in a clean, minimal environment to reduce the possibility of
errors, and rebooting into that - and for that matter, out of it again
into the updated system when complete - is the easiest and safest way
to get there. We've talked about it at some length with no good
solution so far. So, don't be disappointed if your report doesn't get
attention right away - it's a known problem, but we don't know what to
do about it.
Fedora Project Leader
test mailing list -- test(a)lists.fedoraproject.org
To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
Sent from my Android device with K-9 Mail. Please excuse my brevity.