On Fri, Dec 20, 2019 at 8:52 PM L A Walsh
On 2019/12/20 17:32, Knurpht-openSUSE wrote:
Linda, to cut a long story short: Mirrors are there for distributing the transfers for people downloading, updating, upgrading etc. If a workaround for this would go public, everyone would try download.o.o with some options first. Result: download.o.o down.
---- Usually the sites I d/l are fine and give me my max d/l speed -- not always the same for d.o.o. I certainly don't mind using a local mirror if one exists, but most importantly, is really a mirror and not 4+ days behind. Problem now, is I keep getting rerouted to what would normally be a very close, performant mirror, but now, I have no way of getting to "correct content" as I seem to have no choice in the mirror chosen, nor a way to work around it. d.o.o is effectively offline for anyone using a mirror less than or equal to the net-distance of kernel.org from anywhere.
A four day lag time seems like alot for a distro like TW that updates as often as daily.
We may need some faster mirroring though for TW. Sometimes it comepletely rebuilds ( i.e. full package upgrade, f.e. gcc major version upgrade ) , a new release gets distributed before some mirrors have synced the previous released TW repos.
That's a big problem for anyone trying to pull down a coherent release considering the size. I haven't been able to pull down a coherent release since I switched to TW. Sometimes I've gotten remarks from some who when noticing the the noncoherence think it has something to do with changes I've made, but reality is that most of it now has to do with not being able to get a complete copy before another version is released.
This supports one of my long time pet-peeves of having specific versions built into everything that they will work with and not a range or 'newer than or equal to Vx.y'. While many people come up with lots of edge cases where that system can fail. The reality I've run into is often ending up with different parts of the system that not only won't load or run, but more often -- that can't even be built from "open source[sic]" because the sources don't stay still long enough to download all of them and their deps.
Certainly, its beginning to more and more seem like version requirements and differences are becoming more of a problem noticed by more people. Certainly -- with something like TW, might not cutting back to 1/week help resolve a problem? It's hard to get everything in TW working together if the versions of everything are interlocked.
openSUSE Tumbleweed does not move fast enough for mirrors to fail to keep up if they were following the recommended procedure and schedule for maintaining an openSUSE mirror. On average, we see roughly 3 snapshots a week, and in many cases, we see fewer. The problem is that YaST configures repositories on openSUSE to use the download redirector from MirrorBrain, rather than the mirrorlist. The redirector just passes you forward to a "reasonably fresh" mirror and does no further validation. From there, you're at the mercy of the mirror. There are ways to solve this problem, but because it's difficult to get YaST to change its behavior, fixing it will be quite tough. For my personal Tumbleweed systems (where I use DNF instead of Zypper as my package manager), I have an RPM installed that installs me a repo configuration that uses the metalink provided by MirrorBrain so I get a list of mirrors, DNF can do validation and selection of mirrors, and it can download packages in parallel from multiple sources, if need be. This has drastically improved the quality of service I get for software management on openSUSE. And for what it's worth, this is how system repos have been done in Fedora for over a decade. -- 真実はいつも一つ!/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org