On Wed, 8 Feb 2006, Boyd Lynn Gerber wrote:
We should probably delay the redirection on download.openSUSE.org and have the user browse the local ftp tree and only redirect on file request, to make sure he can take all files that are available into account. ATM d.o.o redirects as early as possible, i.e. if you access http://d.o.o/somepath it will redirect you to a server that has the path. But that server might not have all the files that are actually available...
Yes, sometimes the server only has some or a subset of what is needed for doing a YaST inst. I was trying to do an internet installation using a user.sel file as a starting point. I had over 20 packages that could not be installed because the were not on the server I was directed to. I have noticed on some upgrades that the files are unavailable as well.
So you didn't use download.openSUSE.org as your installation source, but used download.openSUSE.org to find a mirror and than c&p'ed it to be the installation source. Right? [If you had used download.openSUSE.org all the way, it should have choosen different mirrors for different files, because it has a local cache where it stores all the information about the status of all files on all servers.] To the server admins: If you feel you don't get enough or too much traffic, please contact me (of list), so I can do some fine tuning. ATM all request directed at download.openSUSE.org are distributed equally amongst our "primary" mirrors. If there is interest in this topic, I might prepare some slides to give a "speed talk" on this at FOSDEM.
The inital usecase for d.o.o (when I did the first implementation) was to have a generic URL for the announcements and to point the installer (YaST) to. But it actually seems people try to browse the inst-sources with it -- and end up on mirrors that are not completely in sync -- right?
Yes!
Alright, I'll put this onto my agenda... Regards Christoph