http://bugzilla.opensuse.org/show_bug.cgi?id=1194196 http://bugzilla.opensuse.org/show_bug.cgi?id=1194196#c1 Andreas Stieger <Andreas.Stieger@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Andreas.Stieger@gmx.de --- Comment #1 from Andreas Stieger <Andreas.Stieger@gmx.de> --- Adding some clarification so we know what we are speaking about... Mirrors not being up to date is expected under normal operations, and the download.opensuse.org interface is build to compensate and offer the correct user experience here. The mirrorbrain redirector on download.opensuse.org will only redirect to mirrors are known to have the most recent files, and will serve most repository meta files directly. So if one mirror stops syncing your particular project it is a non-issue as far as the user-visible interface is concerned - as long as the recommended download.o.o entry point is used. Further, each mirror can independently determine their replication frequency and scope. Repositories under home: are simply less interesting for most mirrors seeking to offer bandwidth (actually often also campus mirrors seeking to serve directly from their own networks) Repositories for CentOS even less so. Ultimately this is a matter of space. If you check your other repositories you will see that some of them are not mirrored anywhere at all. So in this case we have a repository path which is not generally interesting for public mirrors, so fewer mirrors of which one has stopped syncing. So lack of mirrors means a lower likelihood that all of them will be current. With that being said, what is the user-visible problem or problem that you are attempting to solve with this report? a) widehat being listed despite no longer resolving - that is a given b) any particular mirror NOT accessed through download.opensuse.org ... that is not an issue unless you see redirects that should not happen c) ... lack of mirrors? You could attempt to request a top-level project outside of the home: namespace or serve the files/packages through github releases / github packages Anything else? -- You are receiving this mail because: You are on the CC list for the bug.