If I can make a suggestion, that seems way over the top (ie, worse than mine;) ). When you start up package management, it must take forever to refresh that list. Packman 5 times is, at the very least, 3 too many and probably 4 too many.
In this circumstance I would, for example, choose one Packman that you though had a good chance of working and disable the rest (not delete, in case you get it wrong, not just set to a low priority (a high number), because that will still take ages to refresh, but disable).
After that, I’d go through the rest and see what else I could remove (I think I wanted 1 package from server monitoring and nothing else, and you could make a case for disabling that repo once you had that one package, although that does sacrifice updates).
If in doubt, I would check what repo a particular package comes from here and use that. Adding duplicates is only likely to add to the problems if a repo flakily appears and disappears.
I applied the solution from there in both gecko browsers and both work well now:-
In firefox: In firefox address bar - about:config
Look for … network.dns.disableIPv6 and set it to “true”.
Does this mean that my ISP or network connection doesn’t support IPV6???
This is ‘correct’ behaviour, if one method does not work. If you have both, it has to do one first. Therefore, when it tries whichever it tries first is tried and waited for, until a timeout value is reached (which has to be quite a large value, if the method is to have a chance of success on a slow connection, which may or may not be an issue that you have, but unless it is set to this ‘safe’ slow value, it will fail totally for those who do have a slow connection). This makes name look up slow, and is a performance problem and, unfortunately, is really quite common.