Indeed, as I wrote in a previous email, this is how I got Voyage installed too in my Pharo4 devel environment, and it went fine too. Therefore the configuration should be ok. So this is weird. It should not be package cache related because I build image with a completely emptied build directory environment. So I am lost. As A matter of fact, I ran the installation script with a Pharo5 image, and now I get another error during the installation process. See bug log. The repo config is the git one, as described in the first email of this thread. Hilaire Le 25/03/2017 à 20:32, Esteban Lorenzano a écrit :
I just did this:
Gofer new smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo60'; configurationOf: 'VoyageMongo'; loadStable.
(which is the same to the one you did)
in a fresh Pharo4 and it loaded fine. No UnQLite (which is correct). Now, I guess Metacello looks for all packages in baseline even if after it will not download them⦠maybe you are seeing this lookup, but it shouldnât affect you.
So, I guess there is a problem somewhere, but not in the config or the installation. Maybe a package cache problem?
Esteban
-- Dr. Geo http://drgeo.eu