Thanks for reporting this. You raise a valid point. Regarding the length of the time out I know that the developer of update-manager is working on making this shorter in a future version. The particular error you are seeing is caused by a problem on the repository server, not something that update-manager can do a lot about. You shouldn't need to edit your sources.list update-manager does this for you and it looks like it has worked correctly. This is really seems to be a case of bad luck, the server may have been down or overloaded just at the time you tried to upgrade. However I agree that this could be reported better so I will add this to the wishlist. The best solution for this type of error is usually to just try again later
Thanks for reporting this. You raise a valid point. Regarding the length of the time out I know that the developer of update-manager is working on making this shorter in a future version. The particular error you are seeing is caused by a problem on the repository server, not something that update-manager can do a lot about. You shouldn't need to edit your sources.list update-manager does this for you and it looks like it has worked correctly. This is really seems to be a case of bad luck, the server may have been down or overloaded just at the time you tried to upgrade. However I agree that this could be reported better so I will add this to the wishlist. The best solution for this type of error is usually to just try again later