Koozali.org: home of the SME Server

The problem when i install the SME 7.05 rpm package on RHEL4

mark_bj

The problem when i install the SME 7.05 rpm package on RHEL4
« on: October 25, 2005, 04:09:15 PM »
The case is when i install the rhel 4 then install the SME RPM package, surprise, the related packages are missed, like e-smith-base is miss, any e-smith package can't install until e-smith-base has been install, how can i solve tis dependance problem? Thank you.

Offline stefan24

  • *****
  • 483
  • +0/-0
    • www.sme-server.de
The problem when i install the SME 7.05 rpm package on RHEL4
« Reply #1 on: October 25, 2005, 04:18:26 PM »
Then just install e-smith base!

BTW: SME 7.05 is based on RHEL4 (or CentOS 4.1, which is a clone of RHEL4). But it is not intended, that you run SME on top of RHEL4, but to install SME 7.05 from the ISO file.

mark_bj

Reply stefan24
« Reply #2 on: October 26, 2005, 04:05:10 AM »
I have try it but the rpm dependants "server-manager-image" is missed. Can you give me any solution for this way.
Regards,
Mark

Offline gordonr

  • *
  • 646
  • +0/-0
    • http://www.smeserver.com.au/
Re: Reply stefan24
« Reply #3 on: October 26, 2005, 05:58:40 AM »
Quote from: "mark_bj"
I have try it but the rpm dependants "server-manager-image" is missed. Can you give me any solution for this way.
Regards,
Mark


You will have to work through the comps.xml file and all of the dependencies in the set of SME Server packages. This is not going to be a small task and cannot be done one package at a time. It's a large package set, with a complex set of dependencies to support smooth upgrades.

IMO, a better option, if you need to use RHEL4 as the base, would be to build an ISO with all of the RHEL4 packages instead of the CentOS 4.1 equivalents.

However, since the packages in CentOS are simply recompilations of the RHEL4 packages, I'm not sure what you're gaining.

You haven't told us why you want to attempt this, but it certainly wasn't something we planned when we put together the SME Server. As Stefan said, it is designed for installation from CDROM, not for layering on top of an existing installation.

Why do you want to do this?
............

mark_bj

Reply gordonr
« Reply #4 on: October 26, 2005, 08:33:19 AM »
I have some problem set below:
1) what is IMO?,
2) How can i work through the compus.xml file?
Hope be help.
Regards,
Mark

mark_bj

Reply gordonr
« Reply #5 on: October 26, 2005, 08:41:36 AM »
I have some problem set below:
1) what is IMO?,
2) How can i work through the compus.xml file?
Hope be help.
Regards,
Mark

Offline gordonr

  • *
  • 646
  • +0/-0
    • http://www.smeserver.com.au/
Re: Reply gordonr
« Reply #6 on: October 26, 2005, 08:47:24 AM »
Quote from: "mark_bj"
I have some problem set below:
1) what is IMO?,
2) How can i work through the compus.xml file?
Hope be help.
Regards,
Mark


Sorry.

1) IMO == In My Opinion

2) What I meant was you're going to have work out how to do this yourself by reading the CentOS/base/comps.xml and working out what packages you need.

Why do you want/need to do this?
............

mark_bj

Reply gordonr
« Reply #7 on: October 26, 2005, 09:26:24 AM »
Oic .. i am try it before, but also can't resolve the dependencies problem, for example : e-smith-apache is depend on e-smith-base, and e-smith-base depend on "server-manager-image", since e-smith-base is e-smith root package, and e-smith-base need the package server-manager-image install before, the problem can't solve. And the case is that since a company request using qmail and cluster, the problem is that the existing network using "dot" between the first name and last name, and want to single login, clearly, this is the died point inside SME server, thus i want to using SME package on the top of RHEL. Thank you for your help.
Regards,
Mark

Offline gordonr

  • *
  • 646
  • +0/-0
    • http://www.smeserver.com.au/
Re: Reply gordonr
« Reply #8 on: October 26, 2005, 09:53:59 AM »
Quote from: "mark_bj"
Oic .. i am try it before, but also can't resolve the dependencies problem, for example : e-smith-apache is depend on e-smith-base, and e-smith-base depend on "server-manager-image", since e-smith-base is e-smith root package, and e-smith-base need the package server-manager-image install before, the problem can't solve.


I'm very familiar with the dependency issues, and I believe it's going to be hard. I can't provide any further advice other than you're in for a very long road.

Quote from: "mark_bj"

And the case is that since a company request using qmail and cluster,


I believe you'd be better adding the cluster tools to the SME Server install than trying the other way around. This has been raised previously.

Quote from: "mark_bj"

the problem is that the existing network using "dot" between the first name and last name, and want to single login, clearly, this is the died point inside SME server, thus i want to using SME package on the top of RHEL. Thank you for your help.
Regards,
Mark


The first.last account name limitation is built into the SME Server code, not RHEL or CentOS. It won't make any difference at all whether you install on RHEL or CentOS. As I said previously, replacing the CentOS RPMs with the RHEL equivalent RPMs should result in a system which functions identically. If it doesn't, it's a bug.

We automatically create first.last pseudonyms for accounts, but if we need to support first.last account names, that needs to be raised as a new feature request.
............

Offline gordonr

  • *
  • 646
  • +0/-0
    • http://www.smeserver.com.au/
Re: Reply gordonr
« Reply #9 on: October 26, 2005, 11:07:44 PM »
Quote from: "gordonr"

I'm very familiar with the dependency issues, and I believe it's going to be hard. I can't provide any further advice other than you're in for a very long road.


Actually, I will give one final piece of advice on this:

mount the cd
cd /mnt/cdrom/CentOS/RPMS
rpm -Uvh --test *.rpm

rpm will complain about RPMs which are already installed. Weed those from the list and try again. rpm will then complain about duplicate RPMs (i386/i586/i686). Weed the other architectures from the list and try again.

Lather, rinse, repeat.

When you finally whittle down the package set, run "rpm -Uvh <listofrpms>" and then follow-up here with details.

Alternatively, list all of the RPMs and work out which ones are currently installed. Remove those from the list and try upgrading the rest.
............

mark_bj

Reply gordonr
« Reply #10 on: October 27, 2005, 02:30:46 PM »
Thank you for your help.