clpm issueshttps://gitlab.common-lisp.net/clpm/clpm/-/issues2020-05-31T17:43:21Zhttps://gitlab.common-lisp.net/clpm/clpm/-/issues/1Validate HTTPS certificates on Windows2020-05-31T17:43:21ZEric TimmonsValidate HTTPS certificates on WindowsOpenSSL does not seem to automatically connect to the Windows certificate store. We need to figure out how to do that, bundle reasonable certificates with CLPM for Windows, and/or provide a way for users to supply their own certificates.OpenSSL does not seem to automatically connect to the Windows certificate store. We need to figure out how to do that, bundle reasonable certificates with CLPM for Windows, and/or provide a way for users to supply their own certificates.https://gitlab.common-lisp.net/clpm/clpm/-/issues/2Is it possible to store config locally in the project's dir?2020-05-31T18:13:19ZAlexander ArtemenkoIs it possible to store config locally in the project's dir?I want to pin versions of Quicklisp and Ultralisp for each project, not system-wide.
Don't see the ability to do this.
Also, it would be nice to install all libraries into a separate directory, as Qlot does.
This will limit the possib...I want to pin versions of Quicklisp and Ultralisp for each project, not system-wide.
Don't see the ability to do this.
Also, it would be nice to install all libraries into a separate directory, as Qlot does.
This will limit the possibility that multiple projects will interfere with each other by dependencies.https://gitlab.common-lisp.net/clpm/clpm/-/issues/3Develop a test suite2021-09-14T22:42:26ZEric TimmonsDevelop a test suiteThe behavior of CLPM has gotten complex enough that it is no longer suitable to just test it through use. The refactoring of the client and CLI code in v0.3.0 should make the development of a test suite much less painful than it would ha...The behavior of CLPM has gotten complex enough that it is no longer suitable to just test it through use. The refactoring of the client and CLI code in v0.3.0 should make the development of a test suite much less painful than it would have been before.v0.4https://gitlab.common-lisp.net/clpm/clpm/-/issues/4Add extensible architecture for client <-> core communication2021-08-30T00:56:54ZEric TimmonsAdd extensible architecture for client <-> core communicationThe first use case of this would likely be to allow the client to compile the core from source if necessary. Future extensions may include communication over a socket to a persistent CLPM server or using a single CLPM process for every r...The first use case of this would likely be to allow the client to compile the core from source if necessary. Future extensions may include communication over a socket to a persistent CLPM server or using a single CLPM process for every request from the client instead of spawning a new one every time.https://gitlab.common-lisp.net/clpm/clpm/-/issues/5Add API to modify configuration files and clpmfiles2021-08-30T00:57:37ZEric TimmonsAdd API to modify configuration files and clpmfilesCurrently, those files need to be edited by hand. An issue with exposing an API to do it will likely be dealing with comments in these files. A first version may work only by appending to a file to avoid this complication.Currently, those files need to be edited by hand. An issue with exposing an API to do it will likely be dealing with comments in these files. A first version may work only by appending to a file to avoid this complication.https://gitlab.common-lisp.net/clpm/clpm/-/issues/6Add API to remove requirements from contexts2021-08-30T00:57:51ZEric TimmonsAdd API to remove requirements from contextsThis issue focuses on global contexts, as bundles are likely covered by #5This issue focuses on global contexts, as bundles are likely covered by #5https://gitlab.common-lisp.net/clpm/clpm/-/issues/7Update windows path on readme2020-11-18T00:22:29ZWilfredo Velázquez-Rodríguezzulu.inuoe@gmail.comUpdate windows path on readmeIn the readme for configuration there's the path `C:\Users\$USER\AppData\Local\config\clpm\sources.conf`
I think it should be updated to either `C:\Users\%USERNAME%\AppData\Local\config\clpm\sources.conf` or even better `%LOCALAPPDATA%\c...In the readme for configuration there's the path `C:\Users\$USER\AppData\Local\config\clpm\sources.conf`
I think it should be updated to either `C:\Users\%USERNAME%\AppData\Local\config\clpm\sources.conf` or even better `%LOCALAPPDATA%\config\clpm\sources.conf` so that
1. I can use this path directly on my shell/explorer (since env vars are expanded)
2. By using `LOCALAPPDATA` it'll respect non-default AppData locations (SSD + HDD)
Thanks!https://gitlab.common-lisp.net/clpm/clpm/-/issues/8Link to clpm-demo does not exist2020-11-15T16:08:37ZJason LeglerLink to clpm-demo does not existI am running through the tutorial and the link to [clpm-demo](https://gitlab.common-lisp.net/clpm/clpm-demo) doesn't exist.I am running through the tutorial and the link to [clpm-demo](https://gitlab.common-lisp.net/clpm/clpm-demo) doesn't exist.https://gitlab.common-lisp.net/clpm/clpm/-/issues/9Use vendored paths on Windows instead of straight XDG2021-03-17T02:36:18ZEric TimmonsUse vendored paths on Windows instead of straight XDG`uiop:xdg-{cache,config}-home` return paths such as `%LOCALAPPDATA%\cache` on Windows. This is not the standard practice on Windows, so consider moving our cache and config under the `%LOCALAPPDATA%\clpm` folder instead.`uiop:xdg-{cache,config}-home` return paths such as `%LOCALAPPDATA%\cache` on Windows. This is not the standard practice on Windows, so consider moving our cache and config under the `%LOCALAPPDATA%\clpm` folder instead.v0.4https://gitlab.common-lisp.net/clpm/clpm/-/issues/10fatal error encountered; core was built for different runtime [sbcl-2.0.10] [...2020-12-03T22:54:28Zkinopefatal error encountered; core was built for different runtime [sbcl-2.0.10] [clpm-v3.5.0]When running `clpm client source-registry.d` at the command line the output is:
```
fatal error encountered in SBCL pid 85565(tid 0x7f19b41adb80):
core was built for runtime "-builduser-2020-11-10-15-56-55" but this is "buildkitsandbox-...When running `clpm client source-registry.d` at the command line the output is:
```
fatal error encountered in SBCL pid 85565(tid 0x7f19b41adb80):
core was built for runtime "-builduser-2020-11-10-15-56-55" but this is "buildkitsandbox-root-2020-03-30-00-26-04"
```
I'm using the prebuilt binary `https://files.clpm.dev/clpm/clpm-amd64-linux-gnu-v0.3.5.tar.gz`.
I have also successfully installed the source build, but when issuing `clpm client source-registry.d` I am simply dropped into the SBCL REPL w/ no other output.
My SBCL is stock, fresh from the Arch Linux official package repository, no .sbclrc.
```
$ sbcl --version
SBCL 2.0.10
```
```
$ uname -srmo
Linux 5.9.10-zen1-1-zen x86_64 GNU/Linux
```https://gitlab.common-lisp.net/clpm/clpm/-/issues/11Add and document more build options2021-02-22T16:56:48ZEric TimmonsAdd and document more build optionsRight now, CLPM builds using Shinmera's Deploy library and bundles its external dependencies as shared objects which are opened on CLPM start. This way was chosen to make it easier to install CLPM on an arbitrary machine without worrying...Right now, CLPM builds using Shinmera's Deploy library and bundles its external dependencies as shared objects which are opened on CLPM start. This way was chosen to make it easier to install CLPM on an arbitrary machine without worrying about having the correct versions of libraries installed. We should add at least two more build options as well:
+ Static executable. While it's relatively easy to statically link most libraries into the SBCL runtime, creating a static executable is not as easy. But @etimmons has patches to SBCL that allow this (last submitted to sbcl-devel [in June](https://sourceforge.net/p/sbcl/mailman/sbcl-devel/thread/CAOrNaswzf%3DugEwfaEMmrNi3rKC4sNdFdH%2B1kFkYBN3fpp54e9w%40mail.gmail.com/#msg37060632)). Make this the default build for releases as we'd no longer need to distinguish between glibc and musl and there would be fewer files needed to run the executable.
+ Dynamic executable without bundled libs. This would be particularly useful when included CLPM in an OS package manager as the package manager would handle making sure all deps are installed and they are the correct versions.v0.4https://gitlab.common-lisp.net/clpm/clpm/-/issues/12General Common Lisp questions about ~/.config/common-lisp/source-registry.con...2021-01-08T01:28:14ZJason LeglerGeneral Common Lisp questions about ~/.config/common-lisp/source-registry.conf.d/20-clpm-client.confThe files in the `source-registry.conf.d` file are not evaluated as lisp statements as far as I can tell. They appear to be a config DSL. I am trying to figure out how I can dynamically point at my clpm client path instead of hard-codi...The files in the `source-registry.conf.d` file are not evaluated as lisp statements as far as I can tell. They appear to be a config DSL. I am trying to figure out how I can dynamically point at my clpm client path instead of hard-coding it in a config file so I can build it into my [asdf-vm](https://asdf-vm.com) plugin for sbcl. It's proving to be a bit of a nightmare. I am sure I haven't given you enough context, but any ideas you have would be appreciated. Also, if you don't have time to deal with this, feel free to just close this ticket. I am just at my wit's end.https://gitlab.common-lisp.net/clpm/clpm/-/issues/13SBCL readably prints BASE-STRING using array syntax2021-02-22T16:55:50ZEric TimmonsSBCL readably prints BASE-STRING using array syntaxSee:
```common-lisp
CL-USER> (with-standard-io-syntax (print (coerce "hi" 'base-string)))
#A((2) BASE-CHAR . "hi")
```
This can cause issues when running the CLPM client from Lisps that don't understand this syntax. Should probably r...See:
```common-lisp
CL-USER> (with-standard-io-syntax (print (coerce "hi" 'base-string)))
#A((2) BASE-CHAR . "hi")
```
This can cause issues when running the CLPM client from Lisps that don't understand this syntax. Should probably remove `with-standard-io-syntax` in the client repl entry function.Eric TimmonsEric Timmonshttps://gitlab.common-lisp.net/clpm/clpm/-/issues/14asdf-configure-source-registry seems to not like CL_SOURCE_REGISTRY being def...2021-02-22T16:54:43ZJason Leglerasdf-configure-source-registry seems to not like CL_SOURCE_REGISTRY being definedI am not totally sure what is going on, so don't let the title of this lead you astray if you suspect something else is going on.
The issue that I am running into is that I am trying to set CL_SOURCE_REGISTRY via an asdf plugin I am w...I am not totally sure what is going on, so don't let the title of this lead you astray if you suspect something else is going on.
The issue that I am running into is that I am trying to set CL_SOURCE_REGISTRY via an asdf plugin I am working on per your suggestion on issue https://gitlab.common-lisp.net/clpm/clpm/-/issues/12. When I do it, and then try to load a system, it gets into a state where it expects the CL_SOURCE_REGISTRY to be a list.
For example, let's say I want to download lake and install it without using roswell. I clone the repo, cd into it, and run the following command:
```bash
clpm exec --context=lake -- sbcl \
--eval '(setf clpm-client:*asdf-system-not-found-behavior* :install)' \
--eval '(setf clpm-client:*context-diff-approval-method* t)' \
--eval '(asdf:load-system :lake)' \
--eval '(asdf:clear-system :clpm-client)' \
--eval "(sb-ext:save-lisp-and-die \"lake\" :toplevel #'lake/main:uiop-main :executable t :compression 9)"
```
Running that will drop me into the debugger, initially because it can't find lake itself:
```
debugger invoked on a TYPE-ERROR in thread
#<THREAD "main thread" RUNNING {1004AD0243}>:
The value
"/Users/me/.asdf/installs/sbcl/2.0.11/lib/clpm/client/"
is not of type
LIST
Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [RETRY ] Retry ASDF operation.
1: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the
configuration.
2: Retry ASDF operation.
3: Retry ASDF operation after resetting the
configuration.
4: [CONTINUE ] Ignore runtime option --eval "(asdf:load-system :lake)".
5: [ABORT ] Skip rest of --eval and --load options.
6: Skip to toplevel READ/EVAL/PRINT loop.
7: [EXIT ] Exit SBCL (calling #'EXIT, killing the process).
(CLPM-CLIENT::ASDF-CONFIGURE-SOURCE-REGISTRY (:SOURCE-REGISTRY (:DIRECTORY #P"/Users/me/.local/share/clpm/sources/clpi/quicklisp.common-lisp-project-index.org_443/projects/trivial-types/2012-04-07/") (:DIRECTORY #P"/Users/me/.local/share/clpm/sources/clpi/quicklisp.common-lisp-project-index.org_443/projects/trivial-indent/2019-10-07/") (:DIRECTORY #P"/Users/me/.local/share/clpm/sources/clpi/quicklisp.common-lisp-project-index.org_443/projects/trivial-features/2020-07-15/") (:DIRECTORY #P"/Users/me/.local/share/clpm/sources/clpi/quicklisp.common-lisp-project-index.org_443/projects/named-readtables/2020-09-25/") (:DIRECTORY #P"/Users/me/.local/share/clpm/sources/clpi/quicklisp.common-lisp-project-index.org_443/projects/lake/2019-12-27/") (:DIRECTORY #P"/Users/me/.local/share/clpm/sources/clpi/quicklisp.common-lisp-project-index.org_443/projects/documentation-utils/2019-07-11/") (:DIRECTORY #P"/Users/me/.local/share/clpm/sources/clpi/quicklisp.common-lisp-project-index.org_443/projects/deploy/2020-09-25/") (:DIRECTORY #P"/Users/me/.local/share/clpm/sources/clpi/quicklisp.common-lisp-project-index.org_443/projects/cl-unicode/2019-05-21/") (:DIRECTORY #P"/Users/me/.local/share/clpm/sources/clpi/quicklisp.common-lisp-project-index.org_443/projects/cl-syntax/2015-04-07/") (:DIRECTORY #P"/Users/me/.local/share/clpm/sources/clpi/quicklisp.common-lisp-project-index.org_443/projects/cl-ppcre/2019-05-21/") (:DIRECTORY #P"/Users/me/.local/share/clpm/sources/clpi/quicklisp.common-lisp-project-index.org_443/projects/cl-interpol/2020-07-15/") ...) "/Users/me/.asdf/installs/sbcl/2.0.11/lib/clpm/client/")
source: (REST SPLICE)
0]
```
If I exit and re-run it, it will compile lake until it hits the first dependency: `flexi-streams`. I run it again and it will drop into the debugger with the same error as above, but for the next dependency. I repeat the whole process through each dependency (trivial-gray-streams and split-sequence), and once they are all satisfied, it will compile and build the binary.
Something about setting CL_SOURCE_REGISTRY seems to be breaking clpm-client::asdf-configure-source-registry. My lisp foo isn't good enough to tell what is going on. I tried to set the environment variable to (:source-registry (:directory "/Users/me/.asdf/installs/sbcl/2.0.11/lib/clpm/client/")), and it still evaluates it as a string.
Let me know if you have any ideas or need more data.https://gitlab.common-lisp.net/clpm/clpm/-/issues/15Install without deploying libssl and libcrypto2021-02-22T16:58:15ZPetter S. StorvikInstall without deploying libssl and libcryptoI wonder if it's possible to install clpm without deploying libssl and libcrypto to `..../lib/clpm/` and instead use the libraries from where it is located when running the build script? What is the reason for deploying the libraries lik...I wonder if it's possible to install clpm without deploying libssl and libcrypto to `..../lib/clpm/` and instead use the libraries from where it is located when running the build script? What is the reason for deploying the libraries like this? In no way meant as criticism, just curious. Thank you for your work, clpm is a great addition to the common lisp community.https://gitlab.common-lisp.net/clpm/clpm/-/issues/16clpm client source-registry.d generates wrong way if symlinked to other direc...2021-02-22T16:55:03ZAlexander Artemenkoclpm client source-registry.d generates wrong way if symlinked to other directoryI've build `clpm` from the sources and symlinked it into `/Users/art/.local/bin/`.
Now when I request settings for the registry, it makes a path relative to a symlink:
```
[art@osx:~]% clpm client source-registry.d
;; -*- mode: common-...I've build `clpm` from the sources and symlinked it into `/Users/art/.local/bin/`.
Now when I request settings for the registry, it makes a path relative to a symlink:
```
[art@osx:~]% clpm client source-registry.d
;; -*- mode: common-lisp; -*-
;; Auto generated by CLPM version 0.4.0-0.14+g2aa742a-dirty
(:directory #P"/Users/art/.local/bin/../lib/clpm/client/")
```
But this directory does not exist:
```
[art@osx:~]% ls /Users/art/.local/bin/../lib/clpm/client/
ls: /Users/art/.local/bin/../lib/clpm/client/: No such file or directory
```
If I call original binary, it creates a correct path:
```
[art@osx:~]% ~/projects/lisp/clpm/build/bin/clpm client source-registry.d
;; -*- mode: common-lisp; -*-
;; Auto generated by CLPM version 0.4.0-0.14+g2aa742a-dirty
(:directory #P"/Users/art/projects/lisp/clpm/build/lib/clpm/client/")
```
```
[art@osx:~]% which clpm
/Users/art/.local/bin/clpm
[art@osx:~]% ls -l $(which clpm)
lrwxr-xr-x 1 art LD\Domain Users 44 Feb 14 21:03 /Users/art/.local/bin/clpm -> /Users/art/projects/lisp/clpm/build/bin/clpm
```https://gitlab.common-lisp.net/clpm/clpm/-/issues/17What is the best way to deal with libraries that use Quicklisp?2021-08-30T01:01:09ZJason LeglerWhat is the best way to deal with libraries that use Quicklisp?I pulled in a library that has a bunch of tests with `(ql:quickload "lisp-unit")` and I can't figure out how to deal with it without modifying the code. What is the best way to deal with that?I pulled in a library that has a bunch of tests with `(ql:quickload "lisp-unit")` and I can't figure out how to deal with it without modifying the code. What is the best way to deal with that?https://gitlab.common-lisp.net/clpm/clpm/-/issues/18Are you wiring this into sly or slime? If so, how?2021-02-22T14:12:18ZJason LeglerAre you wiring this into sly or slime? If so, how?Maybe this is documented somewhere and I have just missed it. Do you wire this up so that sbcl is started with clpm in emacs automatically? If so, what is the best way to do it?Maybe this is documented somewhere and I have just missed it. Do you wire this up so that sbcl is started with clpm in emacs automatically? If so, what is the best way to do it?https://gitlab.common-lisp.net/clpm/clpm/-/issues/19SBCL is unable to find SBCL implementation when using Roswell2021-03-18T16:59:20ZJason LeglerSBCL is unable to find SBCL implementation when using RoswellI am trying out Roswell and when I run clpm, it can't find a lisp implementation. Do you have any suggestions on how I can make it find sbcl via Roswell? Sorry I keep opening tickets with this weird stuff. I'm desperately trying to fi...I am trying out Roswell and when I run clpm, it can't find a lisp implementation. Do you have any suggestions on how I can make it find sbcl via Roswell? Sorry I keep opening tickets with this weird stuff. I'm desperately trying to figure out a workflow that doesn't make me want to burn the world to the ground. Thanks for all your help.
```
debugger invoked on a CLPM-CLIENT:CLPM-ERROR in thread
#<THREAD "main thread" RUNNING {7004A60233}>:
Error interacting with CLPM! Error output:
Backtrace for: #<SB-THREAD:THREAD "main thread" RUNNING {70005B0083}>
0: ((LAMBDA NIL :IN UIOP/IMAGE:PRINT-BACKTRACE))
1: ((FLET "THUNK" :IN UIOP/STREAM:CALL-WITH-SAFE-IO-SYNTAX))
2: (SB-IMPL::%WITH-STANDARD-IO-SYNTAX #<CLOSURE (FLET "THUNK" :IN UIOP/STREAM:CALL-WITH-SAFE-IO-SYNTAX) {24354BB}>)
3: (UIOP/STREAM:CALL-WITH-SAFE-IO-SYNTAX #<CLOSURE (LAMBDA NIL :IN UIOP/IMAGE:PRINT-BACKTRACE) {700570317B}> :PACKAGE :CL)
4: (UIOP/IMAGE:PRINT-CONDITION-BACKTRACE #<SIMPLE-ERROR "Unable to find an installed lisp implementation." {70057030D3}> :STREAM NIL :COUNT NIL)
5: ((FLET "H2" :IN CLPM-CLI/ENTRY:MAIN) #<SIMPLE-ERROR "Unable to find an installed lisp implementation." {70057030D3}>)
6: (SB-KERNEL::%SIGNAL #<SIMPLE-ERROR "Unable to find an installed lisp implementation." {70057030D3}>)
7: (ERROR "Unable to find an installed lisp implementation.")
8: (CLPM/GROVELER::GET-GROVELER-IMPLEMENTATION)
9: (CLPM/GROVELER:MAKE-GROVELER)
10: ((LAMBDA NIL :IN CLPM/RESOLVE:RESOLVE-REQUIREMENTS))
11: (CLPM/SOURCE::CALL-WITH-SOURCES (#<CLPM/SOURCES/FS:FS-SOURCE {700548A193}> #<CLPM/SOURCES/VCS:VCS-SOURCE {7005491503}> #<CLPM/SOURCES/QL-CLPI:QL-CLPI-DUAL-SOURCE {700490A133}>) #<CLOSURE (LAMBDA NIL :IN CLPM/RESOLVE:RESOLVE-REQUIREMENTS) {70055ADDFB}>)
12: ((LAMBDA (CLPM/INSTALL::NEW-CONTEXT) :IN CLPM/INSTALL:INSTALL-REQUIREMENTS) #<unavailable argument>)
13: ((LAMBDA ()))
14: (CLPM/SESSION::CALL-WITH-CLPM-SESSION #<FUNCTION (LAMBDA NIL) {22C7988B}> :OVERRIDE NIL :KEY NIL)
15: (SB-INT:SIMPLE-EVAL-IN-LEXENV (CLPM/SESSION:WITH-CLPM-SESSION NIL (CLPM/INSTALL:INSTALL :PROJECTS (QUOTE NIL) :SYSTEMS (QUOTE ("fiveam")) :ASDS (QUOTE NIL) :NO-DEPS-P NIL :CONTEXT "default" :SAVE-CONTEXT-P ...) (LIST (CLPM/CONTEXT-QUERIES:SOURCE-REGISTRY :CONTEXT "default" :IGNORE-INHERITED-SOURCE-REGISTRY NIL) (CLPM/CONTEXT-QUERIES:INSTALLED-PRIMARY-SYSTEM-NAMES :CONTEXT "default") (CLPM/CONTEXT-QUERIES:VISIBLE-PRIMARY-SYSTEM-NAMES :CONTEXT "default") (CLPM/CONTEXT-QUERIES:EDITABLE-PRIMARY-SYSTEM-NAMES :CONTEXT "default"))) #<NULL-LEXENV>)
16: (EVAL (CLPM/SESSION:WITH-CLPM-SESSION NIL (CLPM/INSTALL:INSTALL :PROJECTS (QUOTE NIL) :SYSTEMS (QUOTE ("fiveam")) :ASDS (QUOTE NIL) :NO-DEPS-P NIL :CONTEXT "default" :SAVE-CONTEXT-P ...) (LIST (CLPM/CONTEXT-QUERIES:SOURCE-REGISTRY :CONTEXT "default" :IGNORE-INHERITED-SOURCE-REGISTRY NIL) (CLPM/CONTEXT-QUERIES:INSTALLED-PRIMARY-SYSTEM-NAMES :CONTEXT "default") (CLPM/CONTEXT-QUERIES:VISIBLE-PRIMARY-SYSTEM-NAMES :CONTEXT "default") (CLPM/CONTEXT-QUERIES:EDITABLE-PRIMARY-SYSTEM-NAMES :CONTEXT "default"))))
17: ((FLET "THUNK" :IN CLPM-CLI/COMMANDS/CLIENT/REPL::CLI/CLIENT/REPL))
18: (SB-IMPL::%WITH-STANDARD-IO-SYNTAX #<FUNCTION (FLET "THUNK" :IN CLPM-CLI/COMMANDS/CLIENT/REPL::CLI/CLIENT/REPL) {21EEC20B}>)
19: (CLPM-CLI/COMMANDS/CLIENT/REPL::CLI/CLIENT/REPL #<unused argument> #<unused argument>)
20: ((LAMBDA NIL :IN "/Users/etimmons/clpm-v0.3.5/cli/entry.lisp"))
21: (CLPM/CONFIG::CALL-WITH-CONFIG-SOURCE #<CLOSURE (LAMBDA NIL :IN "/Users/etimmons/clpm-v0.3.5/cli/entry.lisp") {700438D99B}> :CONFIG-SOURCE NIL :PATHNAME NIL :OPTIONS-HT #<HASH-TABLE :TEST EQL :COUNT 0 {700438D733}>)
22: (CLPM-CLI/ENTRY:MAIN)
23: (DEPLOY::CALL-ENTRY-PREPARED #<FUNCTION CLPM-CLI/ENTRY:MAIN> #<ASDF/PACKAGE-INFERRED-SYSTEM:PACKAGE-INFERRED-SYSTEM "clpm-cli"> #<DEPLOY:DEPLOY-OP >)
24: ((LAMBDA NIL :IN UIOP/IMAGE:RESTORE-IMAGE))
25: (UIOP/IMAGE:CALL-WITH-FATAL-CONDITION-HANDLER #<CLOSURE (LAMBDA NIL :IN UIOP/IMAGE:RESTORE-IMAGE) {700436642B}>)
26: ((FLET SB-UNIX::BODY :IN SB-EXT:SAVE-LISP-AND-DIE))
27: ((FLET "WITHOUT-INTERRUPTS-BODY-14" :IN SB-EXT:SAVE-LISP-AND-DIE))
28: ((LABELS SB-IMPL::RESTART-LISP :IN SB-EXT:SAVE-LISP-AND-DIE))
Above backtrace due to this condition:
Unable to find an installed lisp implementation.
Original condition:
end of file on #<SB-SYS:FD-STREAM for "descriptor 16" {70038FC1E3}>
Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [RETRY ] Retry ASDF operation.
1: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the
configuration.
2: Retry ASDF operation.
3: Retry ASDF operation after resetting the
configuration.
4: [ABORT ] Exit debugger, returning to top level.
(CLPM-CLIENT::CALL-WITH-CLPM-PROC #<FUNCTION (LAMBDA (CLPM-CLIENT::PROC) :IN CLPM-CLIENT:INSTALL) {70038F895B}>)
source: (ERROR 'CLPM-ERROR :WRAPPED-CONDITION C :ERROR-OUTPUT
(UIOP/STREAM:READ-FILE-STRING
(CLPM-PROC-ERROR-PATHNAME PROC)))
0]
```https://gitlab.common-lisp.net/clpm/clpm/-/issues/20Any plans for the M1 Mac now that sbcl support it?2021-09-05T15:40:04ZJason LeglerAny plans for the M1 Mac now that sbcl support it?I can do a build if that would help.I can do a build if that would help.v0.4