On Thu, 2003-10-30 at 09:44, David Krider wrote:
I'm getting really strange behavior when trying to install software with YaST under 9.0. Everything installed fine from the DVD, but now I can't seem to get programs added by it.
First, it won't go to my DVD ROM drive. I can mount my drive (at /media/dvd) manually, so everything seems right, but YaST can't mount it when I choose "DVD" as a source. So YaST is mixed up about its definition of my DVD ROM. How do I correct this?
Furthermore, when I mount the DVD manually, and choose to install software from a directory, it can't see RPM's that I know are there (specfically, rdesktop). It seems that the catalog in YaST's memory is screwed up. How do I clear it out so that it can be reloaded with a new source?
From searching through the source on the .ycp files, it would seem that YaST does a "Pkg::SourceCreate" on new sources, but I can't find this function actually defined in any .ycp file I have on my system. Comparing what YaST modules I have installed against the multitudes of
I've been trying everything to get this working, and I've got nuttin'. NOTHING WORKS ANYMORE. Not YaST. Not YOU. Not my local copy of the DVD, not my local mirror of the updates, not the YaST default update servers. Every package installed with "yast" in the title has been ``rpm -V'ed''. The rpm database has been rebuilt. _Needless_ to say: This is _extremely_ annoying and frustrating. It's almost like the GUI is preventing me from seeing what's available, but I can't figure out how to get it to do anything different. I can't find ANYTHING about this on Google. The "docs" for YaST are next to NOTHING and completely worthless. packages that are in the distro shows I have everything except the internationalization and development packages installed. Doesn't anyone know how this nonsense works? I've not been worried about the whole "YaST" thing as I've come to get acclimated to 8.2, because it was always solid and handled everything. I can install RPM's by hand, but it worries me now -- badly -- that this has happened to my YaST configuration. Regards, dk