Everything is working again. The good news is that this little incident made me think of how vulnerable mintUpdate was. When our repository goes down, mintUpdate doesn't work because it can't access the rules which define which packages correspond to which safety level. To the user, this doesn't make much sense as most updates come from Ubuntu and even though their repositories are fine, the user can't access updates through the default update manager (mintUpdate) anymore.
So to solve this here's a new idea which should make its way into future versions of mintUpdate:
- If the file server is unreachable, mintUpdate should try to find the rules on the web server (we've got two dedicated servers, so we may as well use them
- If the web server is unreachable as well, then mintUpdate should use the rules it already has (they could potentially be out of date, but that wouldn't be such a big deal and it would only happen when both our servers are down).
Also, mintUpdate knows whether the system is connected to the Internet thanks to the fact that it manages to download the rules... so with this new idea, if the system is not connected to the net, it will take twice as long for mintUpdate to know about it... so obviously we'll find a better way to do this as well.
I'll also take the opportunity to look into the refresh problem.