Bugzilla – Bug 156028
Package Manager mis-labelling of repositories as CD's and CD 1 error message when online repository not available.
Last modified: 2007-04-23 15:01:43 UTC
In YaST2, when adding packages or doing refreshes from an online repository, if the repository stops responding or the required file has gone missing between the time of checking it for install and YAST2 reading the package, YaST2 displays an error dialog saying that it was unable to read "CD 1", even though it was not attempting to read any CD's. Clicking on Details correclty shows the url for the repository that was causing the problem. This happens for ftp, http and ISTR NFS resources, if not all resources. This is annoying for experienced users, having to click on details to see where the error was (although looking at the status display it can sometimes be obvious). But for new users it can be a bit confusing and might lead to problems because they will be double checking that CD 1 is in the drive, and might eventually assume that CD 1 is damaged. I think this goes back to the Package Installation screen, which displays each repository name, followed by CD 1. As the repositories are held online on the internet and stored on hard disks, not CD's, the labelling of having the packages on "CD 1" is not very logical and is misleading for inexperienced users. NOTE: I think this has always been the case, and generally I've just ignored it, but doing a factory update today where I kept getting this error every few minutes, it was finally getting on my nerves ;-)
Created attachment 72436 [details] y2logs
The problem here is that we are displaying generic message telling the user on which media number we are looking for a file. The media description files are on the 1st medium -> therefore CD1. For some installation sources it's the only medium ;-)
Sorry, but let's postpone the change to the 10.2 as en enhancement. Thanks
"CD 1" text should be displayed only for a CD source.
*** This bug has been marked as a duplicate of bug 220195 ***
Oops! Sorry, marked wrong bug as a duplicate...
Fixed in yast2-packager-2.15.15 (STABLE), yast2-packager-2.13.167 (SLES10-SP1)
*** Bug 264852 has been marked as a duplicate of this bug. ***