|
Bugzilla – Full Text Bug Listing |
| Summary: | change installation source in yast | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Toni Ferragut <tonif> |
| Component: | YaST2 | Assignee: | Jiri Srain <jsrain> |
| Status: | RESOLVED WONTFIX | QA Contact: | Stanislav Visnovsky <visnov> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | bi.ac, jrobiso2, suse-beta, twerner |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SuSE Linux 10.1 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Toni Ferragut
2006-05-13 14:38:50 UTC
What type of source are you adding? A local one (CD, directory, NFS) or a source from the internet (http, ftp)? My guess is that YaST is downloading the metadata of the installation source which takes some time - especially when using a source from the internet. (In reply to comment #1) > What type of source are you adding? A local one (CD, directory, NFS) or a > source from the internet (http, ftp)? > > My guess is that YaST is downloading the metadata of the installation source > which takes some time - especially when using a source from the internet. > Add a ftp site, the reply from ftp is fast, I prove it again, and the system wait nearly five minutes. I've a PIV - 3.4Ghz and 1Gb RAM. (pd.: sorry for my bad english) I suppose this is not really a bug. However we need some sort of progress or message to show the user something is happening. (In reply to comment #3) > I suppose this is not really a bug. However we need some sort of progress or > message to show the user something is happening. > No crees que sea un bug, bueno ya me diras la definición de bug. Te explico el problema, añado una fuente de instalación, sea ftp, http, o un directorio local, o lo que sea. El sistema parece aceptar esa fuente, pero luego al darle finalizar, el sistema se pasa cinco minutos mas o menos ejecutando procesos, ocupando el 100% de los recursos de la cpu. Los procesos que ejecuta son estos, alternativamente: parse-metadada, zmd y update-status. Que los ejecute durante casi cinco minutos y ocupando un 99% del procesador, no es normal, por mucho que digais. Lo he provado con el sistema limpio, o sea, después de una instalación limpia. En mi ordenador, ya he especificado sus caracteristicas, y en otras dos máquinas diferentes, y hace exactamente lo mismo. PD. escrito en español, lo siento, me expreso mejor. I have the same problem. Whatever of installation source (ftp or http) i adding in yast, adding and show in the list is no problem, but first, when i refresh this new installation source, it takes a lot of time 5-10 min. and after then, when i close the "add install source dialog", it refreshes an takes the same long time again. Although the installation sources are not set to "autorefresh". And after then, when i start yast to add and remove sofware, its the same thing and it refreshes and refreshes... I think this is a bug. I'm having the same problem, only in my case, the darned "Finish" button doesn't finish. It just sits there, and sits there, forever. No 5 or 10 minutes here, I waited a good hour! And my sources were all ftp4.gwdg.de ones, so I know it wasn't their server being down! Also, 'rug service-list' shows more/different sources than Yast's 'change installation source" listing. I confirm this annoying experience on my machine. Yast hangs after confirming any change to the source list - be it a status change, and add or a delete. After clicking "finish", it simply hangs. YaST2 eventually did complete the new source addition - I waited 45 minutes, though. After much discussion on the mailing list, it seems this function is more in need of a Progress Bar than anything else. To add a progress, I'd need rug to give output which would let me realize the progress status. At the momoment, there are callbacks in ZYPP which report progress while creating a source. Naresh, do you think it would be possible to let rug provide some output which YaST could read in order to display progress while storing a source to ZENworks? If you create such option to rug, please, reassign the bug back to me... Is this still valid? Considering the massive improvements to this whole update/repo system in 10.3, I for one would recommend moving this to WONTFIX. Agreed. Also 11.0 is much faster even compared to 10.3. |