cl-docker-images.common-lisp.dev issueshttps://gitlab.common-lisp.net/cl-docker-images/cl-docker-images.common-lisp.dev/-/issues2022-06-09T20:50:23Zhttps://gitlab.common-lisp.net/cl-docker-images/cl-docker-images.common-lisp.dev/-/issues/3ecl: error while loading shared libraries: libffi.so.7: cannot open shared ob...2022-06-09T20:50:23ZAnton Vodonosovecl: error while loading shared libraries: libffi.so.7: cannot open shared object file: No such file or directory```
$ ecl
ecl: error while loading shared libraries: libffi.so.7: cannot open shared object file: No such file or directory
``````
$ ecl
ecl: error while loading shared libraries: libffi.so.7: cannot open shared object file: No such file or directory
```https://gitlab.common-lisp.net/cl-docker-images/cl-docker-images.common-lisp.dev/-/issues/2Clarify: what ASDF is used by the lisp implementations?2022-06-09T08:13:13ZAnton VodonosovClarify: what ASDF is used by the lisp implementations?The web page - https://cl-docker-images.common-lisp.dev/images/development.html - says:
> Additionally, the following Lisp utilities are installed:
>
> ASDF v3.3.4: The source code is located in /usr/local/share/common-lisp/source/as...The web page - https://cl-docker-images.common-lisp.dev/images/development.html - says:
> Additionally, the following Lisp utilities are installed:
>
> ASDF v3.3.4: The source code is located in /usr/local/share/common-lisp/source/asdf. The first time you attempt to use ASDF for anything non trivial, it will upgrade itself to this version.
Does it mean the lisp implementations are configured to use this ASDF installation instead of the default ASDF that comes with the lisp impl?
For example, when a user simply runs `sbcl` or `ccl` does he anyhow get this ASDF v3.3.4 installation, or the default ASDF normally coming with the lisp implementations will be upgraded to that version at some point?
I have tested, SBCL and CCL seem to use different ASDF version, but the wording of this paragraph leaves impression the ASDF version may be overridden for all the implementations.https://gitlab.common-lisp.net/cl-docker-images/cl-docker-images.common-lisp.dev/-/issues/1Notice: This project will be renamed in the coming week(s)2022-01-18T21:44:27ZErik HuelsmannNotice: This project will be renamed in the coming week(s)Hi,
This issue is to notify the owners of this project about an important upcoming change: the common-lisp.net administrators are working to move all hosted project sites to their own domains - at https://cl-docker-images.common-lisp.de...Hi,
This issue is to notify the owners of this project about an important upcoming change: the common-lisp.net administrators are working to move all hosted project sites to their own domains - at https://cl-docker-images.common-lisp.dev/.
To ensure the content of this repository will be correctly deployed to the new domain (instead of the current https://common-lisp.net/project/cl-docker-images/ location), the rename of the repository is required.
No action is required from your side at this point. However, after the rename, you may need to adjust your git "remotes" for any local clones. Also, you may need to verify any triggers in your `.gitlab.yml` files elsewhere in your project, because they may refer to this repository by name.
Last, the old URL will permanently redirect to the new URL. Therefore, all extant links should continue to work. However, we recommend you eventually update all links you have control over to point directly to the new URL.
Kind regards,
Erik Huelsmann
common-lisp.net admin