Hi Norbert, I understand your point of view that others probably share. I also agree the situation is very bad: Inria took too much time to investigate the problem and now, renater also … The question is: would it be really better outside Inria? Maybe ... maybe not … Anyway, there is still an incident open at renater and gtt. My contact will push today to see if we can have an solution soon
> Le 23 nov. 2017 à 10:19, Norbert Hartl <norb...@hartl.name> a écrit : > > Christophe, > >> Am 23.11.2017 um 09:33 schrieb Christophe Demarey >> <christophe.dema...@inria.fr>: >> >> >>> Le 23 nov. 2017 à 09:08, Marcus Denker <marcus.den...@inria.fr> a écrit : >>> >>> We need to exit Inria and do our own infrastructure. >> >> Marcus, could you elaborate? Why do we need to exit Inria? >> Do you have money to pay the infrastructure? Inria provides it for free for >> the Pharo consortium. >> Of course, the problem is super annoying but the problem is not directly >> related to Inria. It is related to Renater (national research and education >> network in France), the network Inria is connected to. An incident is open >> there. I still have no feedback, so cannot say why it takes so much time to >> solve the problem. > > your view might be too technical here. Aren't you the one that does Cargo so > dependencies are well known to you? ;) > The point is that it just does not work and it doesn't matter whose fault > this is. The point is that it is there for a long time and nobody way able to > fix it. Everyone including you is working so hard on the future for pharo. > But this behaviour is like a slap in the face of everyone working for pharo. > You drive away newcomers and people that would like to work with pharo. It is > not possible to download an image or vm or something from smalltalkhub > reliably. > If this is not fully clear let me tell you what I did yesteray. I resurrected > an older project and ported it pharo6. In order to download the image I had > the execute the curl command 6 times in a row and another two times to get a > vm. Then I tried loading the project with metacello and get a debugger > because the downloaded archive is corrupt. I need to open the full debugger > to see which file it is. Then I need to remove the corrupt file from the > package-cache and restart. And yesterdayI had to do this more then 30 (!!!) > times until I could load the full project. > > I think it is completely out of question to wait until is able to fix it. And > if the money of the consortium is not enough to pay such a service then we > need to put in some more. I'm all ears! > > Norbert >
