elpakit
elpakit copied to clipboard
elpakit-test fails
It is my understanding that if I run elpakit-test in a directory that contains an appropriate recipes/package
file, it should attempt a clean setup and run the specified tests.
Given the recipe file:
(org-blog
:doc "Simple blogging via Org-Mode and WordPress"
:files
("org-blog.el"
"org-blog-buffer.el"
"org-blog-wp.el")
:requires
((org "8.0")
(xml-rpc "20130423"))
:test
(:requires
((el-mock "20140219")
(org "8.0")
(xml-rpc "20130423"))
:files
("org-blog-test.el"))
:version "0.13")
When I run elpakit-test, I get the following error:
Debugger entered--Lisp error: (wrong-type-argument stringp cl-struct-package-desc)
intern(cl-struct-package-desc)
(cons (intern (elt package 0)) (vector (version-to-list (elt package 3)) (elt package 1) (elpakit/strip-file-local-vars (elt package 2)) type))
(cons (cons (intern (elt package 0)) (vector (version-to-list (elt package 3)) (elt package 1) (elpakit/strip-file-local-vars (elt package 2)) type)) --cl-v$
(setq --cl-var-- (cons (cons (intern (elt package 0)) (vector (version-to-list (elt package 3)) (elt package 1) (elpakit/strip-file-local-vars (elt package $
(while (consp --cl-var--) (setq package (car --cl-var--) type (car-safe (prog1 package (setq package (cdr package))))) (setq --cl-var-- (cons (cons (intern $
(let* ((--cl-var-- packages-list) (package nil) (type nil) (--cl-var-- nil)) (while (consp --cl-var--) (setq package (car --cl-var--) type (car-safe (prog1 $
elpakit/packages-list->archive-list(((tar . [cl-struct-package-desc org-blog (0 13) "Simple blogging via Org-Mode and WordPress" ((org (8 0)) (xml-rpc (2013$
(let* ((packages-list (let* ((--cl-var-- package-list) (package nil) (--cl-var-- nil)) (while (consp --cl-var--) (setq package (car --cl-var--)) (setq --cl-$
(if (eq :archive (car package-list)) (copy-directory (aget package-archives (cadr package-list)) destination nil t t) (let* ((packages-list (let* ((--cl-var$
elpakit("/tmp/elpakit-archive8409P0z" ("~/src/org-blog/") t)
(let ((archive-dir (make-temp-file "elpakit-archive" t)) process) (elpakit archive-dir package-list t) (setq process (elpakit/emacs-process archive-dir inst$
(let* ((pre-lisp (car (cdr (plist-member --cl-rest-- (quote :pre-lisp))))) (extra-lisp (car (cdr (plist-member --cl-rest-- (quote :extra-lisp)))))) (let ((-$
elpakit-test(("~/src/org-blog/") org-blog-test "t")
#<subr call-interactively>(elpakit-test record nil)
ad-Advice-call-interactively(#<subr call-interactively> elpakit-test record nil)
apply(ad-Advice-call-interactively #<subr call-interactively> (elpakit-test record nil))
call-interactively(elpakit-test record nil)
command-execute(elpakit-test record)
execute-extended-command(nil "elpakit-test")
#<subr call-interactively>(execute-extended-command nil nil)
ad-Advice-call-interactively(#<subr call-interactively> execute-extended-command nil nil)
apply(ad-Advice-call-interactively #<subr call-interactively> (execute-extended-command nil nil))
call-interactively(execute-extended-command nil nil)
command-execute(execute-extended-command)
Yes. Previous versions of elpakit will continue to work... the current releases are heading towards a 2.5 with full multi-package support on top of the new package API. For the stability issues.