> Am 23.08.2022 um 15:46 schrieb s...@clipperadams.com:
>
> I’m not fully understanding the issue.
>
>
>
> Is it that:
>
> The repos are violating the library license (other than the erroneous MIT
> license, which could easily be updated)?
>
>
It does and I don't want to make that right.
> Am 23.08.2022 um 19:30 schrieb PAUL DEBRUICKER :
>
> From my reading, it seems like whoever posted OmniBase to github 9 years ago
> added the MIT license without permission and the OmniBase library remains
> closed source.
>
exactly.
>
>
>
>> On Aug 23, 2022, at 6:46 AM, s...@clippera
docker-pharo-vm, docker image for Pharo VM reached it's v9.0.17-2022.08.24 version.
What's Changed
Update VM version to v9.0.17 by @gcotelli in https://github.com/ba-st/docker-pharo-vm/pull/6
Add doc describing what to do when a new VM is released
Full Changelog: https://github.com/ba-st/docker-p
docker-pharo-runtime, docker image for Pharo reached it's v10.0.1-2022.08.24 version.
What's Changed
Update Pharo image to v10.0.1 by @gcotelli in https://github.com/ba-st/docker-pharo-runtime/pull/6
Update pharo-vm base docker image to v9.0.17
Full Changelog: https://github.com/ba-st/docker-phar
Launchpad, a command-line interface to start, list, and explain the applications available within the image reached it's v4.7.1 version.
What's Changed
Update docker image to use pharo-runtime v10.0.1 fixing problems with source code loading from git repos by @gcotelli in https://github.com/ba-st/
