Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 539677
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T10:09:39+00:00 2026-05-13T10:09:39+00:00

I am installing Hunchentoot on a new machine. This time I thought I would

  • 0

I am installing Hunchentoot on a new machine. This time I thought I would try out Lispy, because it appears to be simplest way of managing the dependencies for Hunchentoot in a standard and hopefully automatic way. However, when I install it, it trips on not being able to verify a key. I have seen ASDF-INSTALL try to use a key before, and I have normally found some way to skip verifying the key. I don’t really need that kind of security, I trust the people distributing these packages, OK? Anyway, in this case there is no restart to skip the key, so rather than dig into the code and hack my way out of it, I was wondering if there is a more correct way to deal with this. I assume Lispy isn’t supposed to be broken and I am using the most standard and supported environment imaginable for Common Lisp: Ubuntu + sbcl. I figure I could make this work, but then again I could just install all the dependencies for Hunchentoot manually using ASDF-INSTALL just as easily, so I figure I’ll give Lispy a shot and do it in a more controlled and correct way. Here’s the actual log of what I did, cutting out most of the in-between 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 #<THREAD "initial thread" RUNNING {AA5E5E9}>:
  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 #<ASDF:LOAD-OP NIL {AAA7F01}> on
              #<ASDF:SYSTEM "lispy" {ABF01E9}>.
  1: [ACCEPT] Continue, treating #<ASDF:LOAD-OP NIL {AAA7F01}> on
              #<ASDF:SYSTEM "lispy" {ABF01E9}> as having been successful.
  2: [ABORT ] Exit debugger, returning to top level.

(LISPY::VERIFY-MAP
 #P"/var/cache/common-lisp-controller/1000/sbcl/local/home/rob/lispy/maps/map.lisp-expr.asc"
 #P"/var/cache/common-lisp-controller/1000/sbcl/local/home/rob/lispy/maps/map.lisp-expr"
 #<PURI:URI http://common-lisp.net/project/lispy/repository/map.lisp-expr>)
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-13T10:09:40+00:00Added an answer on May 13, 2026 at 10:09 am
    • Install gpg
    • wget http://common-lisp.net/project/lispy/key.asc
    • gpg –import key.asc

    You should be good to go.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.