Panic and the encryption
GPG was acting up
Being in the current historical situation that we are in, I can say
that I am a bit jumpy. So when
gpg
started acting up, I was in a mad
scramble to fix it. Panic is not conducive to critical thinking,
who'da thunk?
Can't read email, can't even encrypt the
.tar
files I'm backing
up. It wasn't a fun time. So I decided to reinstall my system. It was
probably time for it anyways.
Going through the motions
I frantically began
tar
'ing up my important folders and flinging
them into the closest flash drives I could find. The evening found me
flashing the latest Devuan Beowulf into another flash drive and
installing it into the OS HDD. This time, my paranoia made me do a
full-disk encryption system, at least for the OS. I also learned that
I need to gently press on the power button for it to work, not press
it all the way in.
After installation, I then needed to do the
building-emacs-from-source
dance, because Devuan packages don't keep
the latest stable sources for
Emacs
.
By the time I was done, the sun had begun to rise.
GPG still broken, and my panic blinded me to the obvious
When I tested the new install, imagine my surprise when GPG was still
giving me errors. What I didn't notice when this first started
happening was that
gpg-agent
was throwing errors. It was throwing
errors with line numbers. It had line numbers and file names.
The goddamn
gpg-agent.conf
file had an error in it and
gpg-agent
refused to run until it was fixed. Goddamn it. Oh well.
At least my disk is fully encrypted now.