Not really. I could add new “data” to the analysis of this issue configuring both lists (comp1 and comp2) as you suggest but I think I’ll do this only if this may help developers somehow on improving OMV LX. As a user, the workaround is to use
$ urpmi --aria2
and hope it can be as resilient as (–wget) the other for very low velocity internet connections.
In fact, in my (limited) point of view, since the list of repositories yields different results if I change
options (wget => aria2 or curl), I think the explanation has to be searched on how urpmi itself deals with this changes, not neccessarily with the repositories themselves.
Mandian, I don’t have a .wgetrc file. I have a .wget-hsts one with no mention to repos at all. This file has only github related data.
If --wget is not working for you on only one computer then you very likely have a problem with that computer that needs to be corrected. Also when all other users report no problem with --wget this also indicates a problem with that one computer.
I have two computers. Initially the problem happened with only one of them, thought it could be a repository updating feature and eventually the problem was actually gone. But now both computers behave equally, and also there is the fact that other downloading options yields different outcomes …
Don’t know what to think.