"... The hell it isn't Canola's fault! THEY made the decision to use a Nokia-operated repository without TESTING it first. Or at least checking the URL spelling!
THEY made the decision to NOT use their own repository. I know they have/had at least one in the past. It worked well enough for some of their experimental non-Canola stuff.
I'm sick of folks not manning up and accepting the blame for fcuking something up!
Nokia and Canola both get EQUAL blame, period."

Hei iball, we did get the blame, we said again (and I even made a joke about our bad karma) the thing that I wanted to explain was:

1. The team itself new about it, we tested a lot but we did find out the problem (actually in the last couple of hours) you right about that
But....
2. It's is not us that choose where it will go. Managers decided that for the first time canola was going to tableteer (almost like a certified app) and it was demanded that it should be on official repositories.

We (employees) warned but we don dictate the rules. therefore there's a slightly difference I would make to the comment, but in the end we indeed have a slice of the blame.

Now what? Lesson learned? I made a full report, including a comparison of visits in the website x emails saying "I couldn't install" and addded a lot of you guys comments here to show them that we really missed out a lot with that move. The thing is people believed it was going to be a matter of hours to be ready again, but it wasnt.

So, following our tradition to be very open, with the report, I got what the dev team wanted, when we are ready, or even a update is ready we will have our own repository and don't even matter if the official ones are in great shape.

We saw pretty clearly, that don't matter who owns the server, if a user clicks on our website and gets a file corrupted, it's our fault. And it's bad for us not for the repository.

It sucks, but it happened again (last time was dependencies madness).

Marcelo