joseph@crunchbang:~/downloads/OfflineBundle$ dpkg-sig --verify armory_0.92.2-testing_ubuntu-64bit.deb
Processing armory_0.92.2-testing_ubuntu-64bit.deb...
Okay, it sounds like my script is putting the armory*.deb file into the offline bundle before signing it. This might be related to the RPi bundle which I also know I fixed, but doesn't seem to have made it into the latest release. Sorry for the inconvenience!
For now, download armory*.deb, verify it, and then copy it into the offline bundle directory (overwrite the existing .deb). Or verify using the signed hash file, which does contain the hashes of the bundle tar.gzs. Instructions for that are on the website download page.
I'm thinking of changing this whole thing so that there is only regular releases (which seem to be done correctly), and then have a bunch of "offline-setup-packs" that can be installed one time for the offline computer, one for each linux distribution. It would be easier than re-creating every bundle for every release, though it's extra steps for the first-time user -- it's probably worth the tradeoff (especially because I can offer a wider array of offline bundles)