Submitted by BerkWood on Mon, 06/08/2009 - 20:25
I am running Fedora 8 and VMin 3.48 I would like to get the latest version on VMin, but I don' see any updates so I thought I would just run install.sh again, but I don't have access to it......
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Mon, 06/08/2009 - 23:52 Comment #1
You shouldn't need to run install.sh .. in fact, that would be bad idea, as it will destroy your existing installation. Instead, you should be able to get updates with a command like :
yum update webmin usermin wbm-* wbt-* ust-*
This has been fixed. But, yes, running install.sh on an already installed system is a phenomenally bad idea (it's not "update.sh", after all). ;-)
Submitted by BerkWood on Fri, 06/12/2009 - 16:13 Comment #4
Checking with both Yum and Virtualmin Packages, it says there are no updates and that I am running the latest version of 3.48-3 which is not the latest version.
Submitted by JamieCameron on Fri, 06/12/2009 - 16:20 Comment #5
What does your /etc/yum.repos.d/virtualmin.repo file contain?
Also, does running "yum list" show any errors?
Submitted by andreychek on Fri, 06/12/2009 - 16:21 Comment #6
Howdy -- if you run:
ls /etc/yum.repos.d
what all do you see in there?
If there is one that appears related to Virtualmin, what are the contents of it?
would it not be practical to have a line in install.sh that prevents users from reinstalling it?
or is this not possible, you must have thought about it?
if
virtualmin exists
exit quickly and go to support
else
go ahead
:) you have noticed my scripting skills
would it not be practical to have a line in install.sh that prevents users from reinstalling it? or is this not possible, you must have thought about it? if virtualmin exists exit quickly and go to support
I think it actually does under some circumstances. But, it's actually kinda hard to know, with confidence what the user is trying to do and whether the install script would actually do any harm.
And, sometimes, the user really does want to install, even though there might be some vestiges of a Virtualmin system sitting around. But, I'll see about making it more hesitant to do any damage.
But, if the system is already configured and working perfectly (in the case of the most popular operating systems), the script will definitely exit, because it will fail when it tries to setup the software repositories (but then it will proceed to break the software repositories, I think...).
OK, so what I'm saying is that the script is phenomenally stupid and should be shot immediately. I've been working on a new version written in Perl that can be a lot smarter. I'm not sure when I'll have time to finish it, though.
Submitted by BerkWood on Fri, 06/12/2009 - 16:49 Comment #9
Well, I feel lame!! the virtualmin.repo was disabled.... Not sure why since I don't have a reason to disable it. Thanks for answering a lame question :)
Submitted by Issues on Sun, 06/28/2009 - 01:25 Comment #10
Automatically closed -- issue fixed for 2 weeks with no activity.