Why does YaST always complain that it can't read CD1 when in fact it can't read an ftp, http or network resource? Surely this is going to be very misleading for new users? When you click on details it says the correct source name, but wouldn't it be better to put the name of the resource that couldn't be read instead of CD1? I've been trying to do a factory update and it keeps barfing on certain files and complaining that CD1 (ftp.gwdg.de) can't be read... It is just getting on my nerves that I keep seeing CD1 when it isn't trying to read a CD ;-) Dave -- "I got to go figure," the tenant said. "We all got to figure. There's some way to stop this. It's not like lightning or earthquakes. We've got a bad thing made by men, and by God that's something we can change." - The Grapes of Wrath, by John Steinbeck
On Wed, 8 Mar 2006, David Wright wrote:
Why does YaST always complain that it can't read CD1 when in fact it can't read an ftp, http or network resource? Surely this is going to be very misleading for new users?
When you click on details it says the correct source name, but wouldn't it be better to put the name of the resource that couldn't be read instead of CD1?
I've been trying to do a factory update and it keeps barfing on certain files and complaining that CD1 (ftp.gwdg.de) can't be read... It is just getting on my nerves that I keep seeing CD1 when it isn't trying to read a CD ;-)
Could you please report this as a bug via bugzilla? TIA! Regards Christoph
On Wed, 8 Mar 2006, Christoph Thiel wrote:
On Wed, 8 Mar 2006, David Wright wrote:
Why does YaST always complain that it can't read CD1 when in fact it can't read an ftp, http or network resource? Surely this is going to be very misleading for new users?
When you click on details it says the correct source name, but wouldn't it be better to put the name of the resource that couldn't be read instead of CD1?
I've been trying to do a factory update and it keeps barfing on certain files and complaining that CD1 (ftp.gwdg.de) can't be read... It is just getting on my nerves that I keep seeing CD1 when it isn't trying to read a CD ;-)
Could you please report this as a bug via bugzilla? TIA!
I think there is a bug already. It's falling back to CD if network install won't work. Hence the message. Steffen
Am Mittwoch, 8. März 2006 12:31 schrieb Steffen Winterfeldt:
On Wed, 8 Mar 2006, Christoph Thiel wrote:
On Wed, 8 Mar 2006, David Wright wrote:
Why does YaST always complain that it can't read CD1 when in fact it can't read an ftp, http or network resource? Surely this is going to be very misleading for new users?
When you click on details it says the correct source name, but wouldn't it be better to put the name of the resource that couldn't be read instead of CD1?
I've been trying to do a factory update and it keeps barfing on certain files and complaining that CD1 (ftp.gwdg.de) can't be read... It is just getting on my nerves that I keep seeing CD1 when it isn't trying to read a CD ;-)
Could you please report this as a bug via bugzilla? TIA!
I think there is a bug already. It's falling back to CD if network install won't work. Hence the message.
No, it isn't it calls the repository itself in Package Manager CD 1... (E.g. ftp.gwdg.de/pub/... CD 1), even though the repository is online and not on a CD. I just think the messages are very misleading... Dave -- "I got to go figure," the tenant said. "We all got to figure. There's some way to stop this. It's not like lightning or earthquakes. We've got a bad thing made by men, and by God that's something we can change." - The Grapes of Wrath, by John Steinbeck
participants (3)
-
Christoph Thiel -
David Wright -
Steffen Winterfeldt