New projects: cl-autowrap, cl-date-time-parser, cl-ledger, cl-paymill, cl-string-match, epigraph, trivial-tco, vgplot.
Updated projects: access, asdf-dependency-grovel, bt-semaphore, cl-6502, cl-async, cl-bencode, cl-cairo2, cl-enchant, cl-fbclient, cl-gendoc, cl-grace, cl-gss, cl-html-parse, cl-opengl, cl-redis, clfswm, closer-mop, clsql-helper, clws, coleslaw, com.informatimago, common-lisp-stat, commonqt, css-selectors, diff, esrap, exscribe, fs-watcher, gbbopen, gendl, hu.dwim.debug, hu.dwim.def, hu.dwim.perec, hu.dwim.quasi-quote, hu.dwim.stefil, hunchentoot, lfarm, lisp-executable, lisp-unit, lquery, macroexpand-dammit, optima, quicksearch, rfc3339-timestamp, shelly, simple-date-time, spinneret, stmx, swank-crew, uiop, uuid, weblocks, weblocks-utils.
Renamed projects: cl-hctsmsl has been renamed hctsmsl.
I built this dist with ASDF 3. In the near future, Quicklisp will provide ASDF 3 on systems where it is not present. Please let me know if you have any trouble loading anything.
If you'd like to search for useful Quicklisp libraries, I encourage you to give Quickdocs a try!
Thank you!
ReplyDeleteGreat!
ReplyDeleteWhat git repository is used for cl-ledger?
Judging from the warings printed by (ql:quickload :cl-ledger :verbose t) I assume the official https://github.com/ledger/cl-ledger?
It has been broken some time ago by backward incompatible API change of local-time library. Functions like LOCAL-TIME:LOCAL-TIME< were renamed to LOCAL-TIME:TIMESTAMP<
The oficial cl-ledger repo has commits attempting to fix that, the not all the references to local time functions were fixed. Thats why (ql:quickload :cl-ledger :verbose t) prints that many warnigs of type
; In PERIODS:TIME-RANGE-END: Undefined type PERIODS::LOCAL-TIME (2 references)
; In PERIODS:TIME-RANGE-BEGIN: Undefined type PERIODS::LOCAL-TIME (2 references)
; In PERIODS:TIME-DIFFERENCE: Undefined function PERIODS::UNIVERSAL-TIME
; In PERIODS:TIME-DIFFERENCE: Undefined function PERIODS::UNIVERSAL-TIME
Loading weblocks errs saying that "Error: Package BABEL not found". Loading babel first and then weblocks works. This is on LispWorks 6.0.1, Windows 7.
ReplyDelete(I also get two stack overflows when loading weblocks, but they offer the restarts "Increase stack by 50%", so I can go on.)
Thanks, I've added babel to weblocks system dependencies, should be ok for future quicklisp dist updates.
DeleteThe macroexpand-dammit library that's being pulled in has bugs. Can this be rolled back to the canonical version by John Fremlin? https://github.com/guicho271828/macroexpand-dammit/issues
ReplyDeleteExamples of broken libs include sexml.
I can confirm what Bill was saying about sexml being broken.
ReplyDeleteI'm trying to follow the lisp web tales tutorial here: http://lispwebtales.ppenev.com/chap02.html#the-basics. The introductory blog example is broken. Precisely following the instructions found here: https://github.com/madnificent/SEXML to use sexml results in the same stack overflow error.
backtrace here. http://pastebin.com/5z3az7hZ