As @fpietrosantii is saying for various reasons (technical as we now use ephemeral hidden services, and of security as the official Tor repository is the only one that includes the latest version of Tor) we switched using the official Tor repository.
During the install script the repository is added to your system (and this happened correctly) and then is fetched the GPG key that the tor project uses for signing the software.This second is the step that is failing that leave your system with the impossibility to verify automatically the packages that fetches from the tor repository.
The fact instead that the /var/globaleaks/torhs is not created is correct; This last version of GlobaLeaks makes useage of the tor control port for creating hidden services and reloading them; the keys are stored in the database of globaleaks and generated few minutes after the globaleaks startup.
I would suggest yo to try to understand why you got a DNS failure on the fetch of the keys (maybe you added some custom firewalling rules?) and re-run these commands:
gpg --keyserver keys.gnupg.net --recv A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89
gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | apt-key add -
Anyway by this morning we are releasing a new package bugfixed on some of the topics involved here and with additional debugging. I will update this post when it will be available.