Roger Oberholtzer wrote:
On Wed, Feb 15, 2017 at 2:14 PM, Andreas Mahel
wrote: On 15.02.2017 12:58, Roger Oberholtzer wrote:
On Wed, Feb 15, 2017 at 11:57 AM, Michael Hirmke
wrote: A nice feature for zypper could be that it tries a mirror, and after a couple failures, it tries the specified repo before failing.
I cannot populate my mirror because I would have to load the files via the same file checker. Every file is checked. My mirror would not contain the suspect files. They are simply not let pass. Unless the external source is on the white list.
If I read Michael's mail correctly, the intention was to split the issue in two aspects. 1. Avoid zypper using random mirrors by pointing it to the one and only internal mirror repository
No problem with that.
2. Limit the firewall exception to exactly one external repo server from which you then mirror the data to your local server.
That is still the question: since all repos are not on all mirrors (like the one I mentioned - but there are many more), I would still need to get the mirror software to talk to an external server. I guess the idea is that mirrors always get data from download.opensuse.org and never from a mirror. SO I only need that in the white list.
I can't help but think that the mirror activity may be more work against download.opensuse.org than my occasional updates...
Private and public mirrors are run from different servers, not from download.opensuse.org. -- Per Jessen, Zürich (3.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org