How to update an package using update-dist?

540 views
Skip to first unread message

Slobodan Milnović

unread,
Dec 10, 2011, 5:00:36 PM12/10/11
to Quicklisp
Hi,

I've tried to update an package using update-dist, but it seems that
update-dist works only for "quicklisp". I've tried it with different
packages but the result is the same (I'm doing it with the latest
quicklisp, updated today).

First I have tried to update the package but there was an error, then
I have tried to update the quicklisp which worked, and then I have
tried to update the package again and got the error again. It's the
same when I restart the slime.

I do realize that the package is now updated with all of the other
packages, but it would be great if I could update separate packages.
The reason that I have tried it in the first place is weblocks. I
wanted to update all the other packages without updating hunchentoot.
Unfortunatelly it didn't work, and I'll have to revert to an older
quicklisp state.

Here is the error. I've managed to replicate it using other packages
too. Or perhaps I'm just using it in an wrong way?

quicklisp 2011-12-03
sbcl 1.0.53
slime 2011-09-28


CL-USER> (ql:system-apropos "postmodern")
#<SYSTEM cl-postgres / postmodern-20111203-git / quicklisp 2011-12-03>
#<SYSTEM cl-postgres-tests / postmodern-20111203-git / quicklisp
2011-12-03>
#<SYSTEM postmodern / postmodern-20111203-git / quicklisp 2011-12-03>
#<SYSTEM s-sql / postmodern-20111203-git / quicklisp 2011-12-03>
#<SYSTEM simple-date / postmodern-20111203-git / quicklisp 2011-12-03>
#<SYSTEM simple-date-postgres-glue / postmodern-20111203-git /
quicklisp 2011-12-03>
#<SYSTEM simple-date-tests / postmodern-20111203-git / quicklisp
2011-12-03>
NIL
CL-USER> (ql:update-dist "cl-postgres")


There is no applicable method for the generic function
#<STANDARD-GENERIC-FUNCTION QL-DIST:AVAILABLE-UPDATE (1)>
when called with arguments
(NIL).
[Condition of type SIMPLE-ERROR]

Restarts:
0: [RETRY] Retry calling the generic function.
1: [RETRY] Retry SLIME REPL evaluation request.
2: [*ABORT] Return to SLIME's top level.
3: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread"
RUNNING {10039B0083}>)

Backtrace:
0: ((SB-PCL::FAST-METHOD NO-APPLICABLE-METHOD (T)) #<unused
argument> #<unused argument> #<STANDARD-GENERIC-FUNCTION QL-
DIST:AVAILABLE-UPDATE (1)> NIL)
Locals:
SB-PCL::ARGS = (NIL)
GENERIC-FUNCTION = #<STANDARD-GENERIC-FUNCTION QL-
DIST:AVAILABLE-UPDATE (1)>
1: (SB-PCL::CALL-NO-APPLICABLE-METHOD #<STANDARD-GENERIC-FUNCTION QL-
DIST:AVAILABLE-UPDATE (1)> (NIL))
Locals:
SB-DEBUG::ARG-0 = #<STANDARD-GENERIC-FUNCTION QL-
DIST:AVAILABLE-UPDATE (1)>
SB-DEBUG::ARG-1 = (NIL)
2: (QUICKLISP-CLIENT:UPDATE-DIST #<unavailable argument> :PROMPT T)
Locals:
QL-DIST:DIST = :<NOT-AVAILABLE>
#:PROMPT-DEFAULTING-TEMP = T
3: (SB-INT:SIMPLE-EVAL-IN-LEXENV (QUICKLISP-CLIENT:UPDATE-DIST "cl-
postgres") #<NULL-LEXENV>)
Locals:
SB-DEBUG::ARG-0 = (QUICKLISP-CLIENT:UPDATE-DIST "cl-postgres")
SB-DEBUG::ARG-1 = #<NULL-LEXENV>
4: (EVAL (QUICKLISP-CLIENT:UPDATE-DIST "cl-postgres"))
Locals:
SB-DEBUG::ARG-0 = (QUICKLISP-CLIENT:UPDATE-DIST "cl-postgres")
5: (SWANK::EVAL-REGION "(ql:update-dist \"cl-postgres\")\n")
Locals:
SB-DEBUG::ARG-0 = "(ql:update-dist \"cl-postgres\")\n"
6: ((LAMBDA ()))
[No Locals]
7: (SWANK::TRACK-PACKAGE #<CLOSURE (LAMBDA #) {10031FE03B}>)
Locals:
SB-DEBUG::ARG-0 = #<CLOSURE (LAMBDA ()) {10031FE03B}>
8: (SWANK::CALL-WITH-RETRY-RESTART "Retry SLIME REPL evaluation
request." #<CLOSURE (LAMBDA #) {10031FDF5B}>)
Locals:
SB-DEBUG::ARG-0 = "Retry SLIME REPL evaluation request."
SB-DEBUG::ARG-1 = #<CLOSURE (LAMBDA ()) {10031FDF5B}>
9: (SWANK::CALL-WITH-BUFFER-SYNTAX NIL #<CLOSURE (LAMBDA #)
{10031FDF2B}>)
Locals:
SB-DEBUG::ARG-0 = NIL
SB-DEBUG::ARG-1 = #<CLOSURE (LAMBDA ()) {10031FDF2B}>
10: (SWANK::REPL-EVAL "(ql:update-dist \"cl-postgres\")\n")
Locals:
SB-DEBUG::ARG-0 = "(ql:update-dist \"cl-postgres\")\n"
11: (SB-INT:SIMPLE-EVAL-IN-LEXENV (SWANK:LISTENER-EVAL "(ql:update-
dist \"cl-postgres\") ..)
Locals:
SB-DEBUG::ARG-0 = (SWANK:LISTENER-EVAL "(ql:update-dist \"cl-
postgres\")\n")
SB-DEBUG::ARG-1 = #<NULL-LEXENV>
12: (EVAL (SWANK:LISTENER-EVAL "(ql:update-dist \"cl-postgres\") ..)
Locals:
SB-DEBUG::ARG-0 = (SWANK:LISTENER-EVAL "(ql:update-dist \"cl-
postgres\")\n")
13: (SWANK:EVAL-FOR-EMACS (SWANK:LISTENER-EVAL "(ql:update-dist \"cl-
postgres\")\n") "COMMON-LISP-USER" 25)
Locals:
SB-DEBUG::ARG-0 = (SWANK:LISTENER-EVAL "(ql:update-dist \"cl-
postgres\")\n")
SB-DEBUG::ARG-1 = "COMMON-LISP-USER"
SB-DEBUG::ARG-2 = 25
14: (SWANK::PROCESS-REQUESTS NIL)
Locals:
SB-DEBUG::ARG-0 = NIL
15: ((LAMBDA ()))
[No Locals]
16: ((LAMBDA ()))
[No Locals]
17: (SWANK-BACKEND::CALL-WITH-BREAK-HOOK #<FUNCTION SWANK:SWANK-
DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {1003B8011B}>)
Locals:
*INVOKE-DEBUGGER-HOOK* = :<NOT-AVAILABLE>
SWANK-BACKEND::CONTINUATION = #<CLOSURE (LAMBDA ())
{1003B8011B}>
SWANK-BACKEND::HOOK = #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK>
18: ((FLET SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK) #<FUNCTION
SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {1003B8011B}>)
Locals:
*DEBUGGER-HOOK* = :<NOT-AVAILABLE>
SB-KERNEL:*HANDLER-CLUSTERS* = :<NOT-AVAILABLE>
SWANK-BACKEND::FUN = #<CLOSURE (LAMBDA ()) {1003B8011B}>
SWANK-BACKEND::HOOK = #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK>
19: (SWANK::CALL-WITH-BINDINGS ((*STANDARD-OUTPUT* . #) (*STANDARD-
INPUT* . #) (*TRACE-OUTPUT* . #) (*ERROR-OUTPUT* . #) (*DEBUG-IO* . #)
(*QUERY-IO* . #) ...) #<CLOSURE (LAMBDA #) {1003B8013B}>)
Locals:
SB-DEBUG::ARG-0 = ((*STANDARD-OUTPUT* . #<SWANK-BACKEND::SLIME-
OUTPUT-STREAM {100386D2E3}>) ...
SB-DEBUG::ARG-1 = #<CLOSURE (LAMBDA ()) {1003B8013B}>
20: (SWANK::HANDLE-REQUESTS #<SWANK::CONNECTION {1002D8ED43}> NIL)
Locals:
SWANK::CONNECTION = #<SWANK::CONNECTION {1002D8ED43}>
SWANK::TIMEOUT = NIL
21: ((FLET #:WITHOUT-INTERRUPTS-BODY-[BLOCK412]417))
[No Locals]
22: ((FLET SB-THREAD::WITH-MUTEX-THUNK))
[No Locals]
Catch-tags:
SB-IMPL::%END-OF-THE-WORLD
SB-INT:TOPLEVEL-CATCHER
23: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-MUTEX]309))
[No Locals]
24: (SB-THREAD::CALL-WITH-MUTEX ..)
Locals:
SB-DEBUG::ARG-0 = #<CLOSURE (FLET SB-THREAD::WITH-MUTEX-THUNK)
{7FFFF4CFECEB}>
SB-DEBUG::ARG-1 = #<SB-THREAD:MUTEX "thread result lock"
owner: #<SB-THREAD:THREAD "repl-thre..
SB-DEBUG::ARG-2 = #<SB-THREAD:THREAD "repl-thread" RUNNING
{10039B0083}>
SB-DEBUG::ARG-3 = T
25: (SB-THREAD::INITIAL-THREAD-FUNCTION)
[No Locals]
26: ("foreign function: call_into_lisp")
[No Locals]
27: ("foreign function: new_thread_trampoline")
[No Locals]

Zach Beane

unread,
Dec 10, 2011, 5:10:14 PM12/10/11
to quic...@googlegroups.com
Slobodan Milnović <slobodan...@gmail.com> writes:

> Hi,
>
> I've tried to update an package using update-dist, but it seems that
> update-dist works only for "quicklisp". I've tried it with different
> packages but the result is the same (I'm doing it with the latest
> quicklisp, updated today).
>
> First I have tried to update the package but there was an error, then
> I have tried to update the quicklisp which worked, and then I have
> tried to update the package again and got the error again. It's the
> same when I restart the slime.
>
> I do realize that the package is now updated with all of the other
> packages, but it would be great if I could update separate packages.
> The reason that I have tried it in the first place is weblocks. I
> wanted to update all the other packages without updating hunchentoot.
> Unfortunatelly it didn't work, and I'll have to revert to an older
> quicklisp state.

There isn't a way to update individual projects within a set in
Quicklisp. They are all versioned together. Reverting to the older
quicklisp state is the recommended way, for now, to make sure you have
things that all work together.

Systems that are available via ASDF take precedence over systems in
Hunchentoot. One option you might investigate is grabbing Weblocks and
an old Hunchentoot and unpacking them in ~/quicklisp/local-systems/ to
see if that works ok. Of course, then other projects that have been
updated to the new Hunchentoot API might not work, but perhaps those
aren't as important to you...

Zach

Slobodan Milnović

unread,
Dec 10, 2011, 5:23:10 PM12/10/11
to quic...@googlegroups.com
Hi, thanks for the answer. I guess I'll revert back for the time
being, and wait for the weblocks to be updated.
Reply all
Reply to author
Forward
0 new messages