Hello, I try to install Virtualmin, but it fails. After a little bit of work YaST pop up and inform me about an unresolved dependency with NX (Proxy-System for X11). Ok, I select them too. Now I start the installation by myself. After the this the scripts says: INFO - Installation completed. But there is no Virtualmin installed, I have Webmin and Usermin, both works fine. But I can't find Virtualmin neither in Webmin nor on the file system.
If I show the selected items during the install I will see that virtualmin is available but not selected. If I try to select it by myself I get about 20 depency warnings which can't be resolved. I use SuSE 9.3 with the newest updates.
Hello,
I solved the problem by myself. After the install I start YaST, reactivated the sources and do the install again with yast -i virtualmin-base. I don't now why, but it seems to work.
Hey Florian,
I'm a little shaky on the yast package manager in 9.3, myself. I've gotten a similar bug report to this one, but I'm not sure exactly what's going wrong. I suspect the bits of scripting I've done using y2pmsh to add and remove repositories isn't working quite right when things go wrong (it's supposed to clean up after itself, so a re-installation won't add extraneous repositories).
The NX dependency issue is the fault of SUSE--we certainly don't need it or ask for it to be installed. The yast package manager in 9.3 is terrible with dependency resolution...I had to rewrite huge swaths of the install.sh to accomodate its refusal to resolve deps automatically (despite the claim that it will--a human has to be involved in that "automatic" process, which pretty much completely defeats the purpose for our needs). SUSE 10.0 is quite a bit better with regards to package management, and I understand they've continued to move in a yum-like direction with something called pug (I think?) in the developing 10.1. I look forward to it, since yast is a bear to script with, and getting rid of the reliance on yast will make the installation much simpler and less error-prone on SUSE systems.
More than you wanted to know, I'm sure. ;-)
Anyway, I'm glad you got it worked out. I'll spend some time with 9.3 ASAP to see if I can replicate this particular issue. I know it exists, since I've heard of it from two users...I just didn't see it during my own testing.
--
Check out the forum guidelines!