Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upSplitGPG fails if VM containing the key is not running #1283
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
I'm experiencing this too. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
Oct 7, 2015
Member
Actually, I think this is some kind of "first-run" issue, because now my GPG backend VMs are autostarting on-demand.
|
Actually, I think this is some kind of "first-run" issue, because now my GPG backend VMs are autostarting on-demand. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Oct 7, 2015
Member
On Wed, Oct 07, 2015 at 03:13:11AM -0700, Axon wrote:
Actually, I think this is some kind of "first-run" issue, because now my GPG backend VMs are autostarting on-demand.
Yes, looks like it. But still it is a bug.
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
On Wed, Oct 07, 2015 at 03:13:11AM -0700, Axon wrote:
Yes, looks like it. But still it is a bug. Best Regards, |
qjoo commentedOct 6, 2015
Expected behavior: GPG key containing VM is started on demand (R2 behavior)
If the VM is already running everything works fine.
This is on R3.0 with the default F21 template.
Traceback ("manual" copy paste :)