Mike wrote:
I have a 9.1 system working great. I want to install a package ("A") that I haven't installed before, so I go to Yast and try to install it.
Note it is not yet installed.
When I select "A", I get dependency errors because in the meantime You has upgraded package "B" that "A" depends on. Yast will let me downgrade "B" (which isn't such a good idea because "B" is all configured and customized) or install "A" and ignore the conflict.
Either will work, as long as you run YOU afterwards.
What is the best way to overcome the situation? There is an upgraded package "A" out there on the update server. Why won't Yast go get that one?
Updates are just that. Yast cannot update a package that is not yet installed. Install it, and Yast Online Update will update it and take care of the dependency problem. If you ignore the conflict, YOU will download the new A package and no more conflict. If you downgrade B, YOU will update both. Results are the same. Just run YOU, as the YAST Package Manager doesn't access the updates. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871