Peter, just to start with I would remove all the duplicated identical data sources.
Then type the data source in your browser and make sure you get a directory/file listing in reply. Lets us all know what happens after this Scott Peter Bradley wrote: > Ysgrifennodd Peter Bradley: >> It's time I got this business of adding installation sources to YaST >> thing sorted. >> >> I'd really like to install the latest versions of Mono and >> Monodevelop, so I went to the web site, which advises SUSE uses to add >> the installation source: >> >> http://go-mono.com/download-stable/suse-100-x86_64 >> >> to YaST. >> >> In YaST --> Software --> Installation Source, I clicked on add --> >> http and, in the dialog that appears added the following details: >> >> Server Name: go-mono.com >> Directory on server: download-stable/suse-100-x86_64 >> >> After clicking OK in the dialog, it went away and thought about it for >> a while and then added 27 identical URLs to the list in the Software >> source media dialog. The URLs added are all listed (immediately after >> the line specifying my installation DVD source) as: >> >> http://go-mono.com/download-stable/suse-100-x86_64 >> >> (which, I guess, is what you'd expect except that I was only expecting >> it to add a single line) >> >> I then turned refresh on for each of these entries and clicked Finish. >> >> Back in the YaST Control Centre I chose Software Management. YaST >> then tried to refresh each of these sources. On every attempt, the >> error message: >> >> ERROR(InstSrc:E_no_instsrc_on_media) >> >> was displayed. Very user friendly, I thought :-) >> >> When I eventually got back to YaST, nothing from this installation >> source appeared to be displayed (i.e. there was nothing I could see >> that indicated that I had any version of Mono available to me except >> 1.1.8x that I had from the installation DVD, and which I had >> uninstalled prior to adding the new source). The source column in >> YaST was empty in all cases. >> >> Finally, just for the heck of it, I turned refresh off and tried >> again. The result was the same. >> >> Does anyone know what the undoubtedly obvious thing is that I've missed? >> >> Thanks, >> >> >> Peter >> > I hope that no-one will mind if I reply to this to bring it back up the > list. I suspect it got lost in the holiday traffic: so if anyone does > have any suggestions, I'd be very pleased to hear. > > Many thanks. > > > Peter >
smime.p7s
Description: S/MIME Cryptographic Signature
