I am installing Hunchentoot on a new machine. This time I thought I would try Lispy, because this is the easiest way to manage dependencies for Hunchentoot in the standard and, hopefully, automatic way. However, when I install it, it shuts down, unable to verify the key. I saw ASDF-INSTALL trying to use the key before, and I usually found a way to skip key verification. I don’t need such protection, I trust the people distributing these packages, okay? In any case, in this case there is no restart to skip the key, so instead of digging into the code and breaking out of it, I was wondering if there is a more correct way to handle this. I assume that Lispy should not be broken, and I use the most standard and supported environment that can be provided for Common Lisp: Ubuntu + sbcl.I suppose I can do this work, but again, I could just install all the dependencies for Hunchentoot manually using ASDF-INSTALL just as easily, so I believe that I will give Lispy a shot and make it in a more controlled and correct way. Here is the actual log of what I did, cutting out most of the intermediate messages:
* (load "asdf-config.lisp")
T
* (asdf:oos 'asdf:load-op :lispy)
; loading system definition from /home/rob/lispy/lispy-0.5/lispy.asd into
...
2010-01-06 23:13:25 "Initializing Lispy system on SBCL 1.0.29.11.debian"
2010-01-06 23:13:25 "Fetching http://common-lisp.net/project/lispy/repository/map.lisp-expr"
2010-01-06 23:13:27 "Fetching http://common-lisp.net/project/lispy/repository/map.lisp-expr.asc"
gpg: Signature made Fri 25 Dec 2009 01:19:20 PM EST using DSA key ID 7CF49723
gpg: Can't check signature: public key not found
debugger invoked on a SIMPLE-ERROR in thread
GPG verification of map /var/cache/common-lisp-controller/1000/sbcl/local/home/rob/lispy/maps/map.lisp-expr with signature /var/cache/common-lisp-controller/1000/sbcl/local/home/rob/lispy/maps/map.lisp-expr.asc failed: "gpg: Signature made Fri 25 Dec 2009 01:19:20 PM EST using DSA key ID 7CF49723
gpg: Can't check signature: public key not found
"
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [RETRY ] Retry performing
1: [ACCEPT] Continue, treating
2: [ABORT ] Exit debugger, returning to top level.
(LISPY::VERIFY-MAP