vicidial.org

Could not find webmin installed in the GoAutodial iso...

tried installing via rpm..

Transaction Check Error:
file /usr/share/man/man3/Switch.3pm.gz from install of perl-5.8.8-32.el5_5.2.i386 conflicts with file from package perl-Switch-2.14-1.el5.rf.noarch

Tried yum update, and same error...

++++
rpm -Uvh *.rpm --force

allowed the install to proceed... - initially there was no ill side effects..
- until I rebooted, and then it stopped working...

Has anyone found a solution?

++++
was using...

goautodial-ce-2.0-final.iso

installed on HP proliant dl360 G3 dual 3.0 xenon 3 gb ram

when you finished installing it, did you add it to the list of programs to start at boot?

if not ... you can start it up and then use it to add it to the "at boot" list ...

and now it is working again from reboot... - and yes it was configured to start on boot up....

webmin not starting issue is much more a red-herring..

needing to rely on --force to get it installed because of a conflict is what I am much more worried about. because a yum update will also fail as a result of this conflict...

webmin on CentOS failing is not so much a GoAutoDial problem as it is a Webmin problem. You need to find the "conflict" (when it fails) and discuss it with Webmin (although if you find the failure, you may also find some wisdom from gardo to resolve it as it may be something resulting from a specific add-on)

I disagree..

Webmin failing is because GoAutoDial uses ..

See the error message that is at the top of thread...

Transaction Check Error:
file /usr/share/man/man3/Switch.3pm.gz from install of perl-5.8.8-32.el5_5.2.i386 conflicts with file from package perl-Switch-2.14-1.el5.rf.noarch

Webmin works quite well, It's on all my other Centos Systems... and has been arround way longer than GoAutoDial...

Webmin WAS working on vicidial.. but not with of GoAutoDial ?? What's with that ?

For me to take GoAutoDial seriously, It needs to work well with it's peers..

Interesting.

CentOS is not supported by The Vicidial Group. This is part of "Why". (And remember, this is all hearsay because *I* am not part of The Vicidial Group, see my signature )

perl is required. When the installer loaded perl, it loaded switch as a "dependency".

but switch conflicts with perl-switch which is required by webmin.

this is a CentOS package conflict, which may or may not be something gardo at goautodial can resolve, but i would not "blame" goautodial for it unless he modified the dependencies of perl-5.8.8 for some reason to use non-standard dependencies.

and make no mistake: I LOVE webmin (Using "Usermin" portion of it to allow clients direct access to "Edit" ANY file on the drive without having to build an 'interface', just right there within webmin ... that's freakin' cool)

BUT: CentOS is not supported for a reason. Apparently "This sort of thing" happens quite a bit. Those who maintain and port the packages to CentOS have a hard job, but they didn't do it well enough to "Sell" Matt. (and apparently that was all before they had ... problems with management we won't talk about).

You can safely ignore the error. The file in question is just the document manual for the perl switch module. It doesn't really affect anything on the system.

Transaction Check Error:
file /usr/share/man/man3/Switch.3pm.gz from install of perl-5.8.8-32.el5_5.2.i386 conflicts with file from package perl-Switch-2.14-1.el5.rf.noarch

how can the doc ... oh! so when you enter "man" it won't know which to pull ... interesting. can that be permanently told to ignore without --force? (so yum updates can succeed without intervention?)

but once again, that's a CentOS issue ... two packages which have arguing manuals.

If you run: man Switch it will display the manual for the perl Switch package. The problem was that 2 packages have the same manual hence the seeming conflict. It's actually the same file being installed by the two pacakges. A packaging bug on the creation of the perl-Switch RPM file.

williamconley wrote:how can the doc ... oh! so when you enter "man" it won't know which to pull ... interesting. can that be permanently told to ignore without --force? (so yum updates can succeed without intervention?)

but once again, that's a CentOS issue ... two packages which have arguing manuals.