Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: wyron on March 07, 2004, 06:13:23 AM
-
Like several others I installed yum om ny new server installation in connection with Clam+Amavis from pagefault (and Thanks awf'y for that howto !!!).
I now have a Yum section in my serer-manager panel.
But how to use it ??
I have added the Yum repository: http://www.ibiblio.org/pub/Linux/distributions/smeserver/releases/development/RPMS/headers/
. . but when I try to check the repository I get: 'Error running yum info update'.
Am I the only one with this problem ??
If so, how to solve it ?
-
Like several others I installed yum om ny new server installation in connection with Clam+Amavis from pagefault (and Thanks awf'y for that howto !!!).
I now have a Yum section in my serer-manager panel.
I also instaled yum from http://pagefault.org/howto/e-smith-antivirus.shtml and then installed the Anti-virus package but I do not have any yum panel in the server-manager. How did you get the yum panel in your server manager?
Bob
-
The Yum section is at the bottom of the server-manager panel.
Are you sure its not there ?
Have you followed through the howto ?
Have you '/sbin/e-smith/signal-event post-update' ?
Have you rebooted ?
-
Like several others I installed yum om ny new server installation in connection with Clam+Amavis from pagefault (and Thanks awf'y for that howto !!!).
I now have a Yum section in my serer-manager panel.
But how to use it ??
I have added the Yum repository: http://www.ibiblio.org/pub/Linux/distributions/smeserver/releases/development/RPMS/headers/
. . but when I try to check the repository I get: 'Error running yum info update'.
Am I the only one with this problem ??
If so, how to solve it ?
Don't include the /headers subdirectory...
-
Like several others I installed yum om ny new server installation in connection with Clam+Amavis from pagefault (and Thanks awf'y for that howto !!!).
I now have a Yum section in my serer-manager panel.
I also instaled yum from http://pagefault.org/howto/e-smith-antivirus.shtml and then installed the Anti-virus package but I do not have any yum panel in the server-manager. How did you get the yum panel in your server manager?
Bob
The other user would have installed Darrel May's yum addon:
rpm -ihv http://www.ibiblio.org/pub/Linux/distributions/smeserver/contribs/dmay/smeserver/6.x/beta/yum/smeserver-yum-1.0.0-03dmay.noarch.rpm
-
I am also getting the "Error running yum info updates" error when I am trying to "check repository" in the Server Manager.
When doing an Yum update at the command line I get the following error messages:
[root@samba root]# yum update
'import site' failed; use -v for traceback
Traceback (most recent call last):
File "/usr/bin/yum", line 22, in ?
import yummain
ImportError: Bad magic number in /usr/share/yum/yummain.pyc
I have no clue how to solve this.
Regards
Knut
-
Since i could not get Darrell's yum to work - it is the one which installs the serverpanel - i stayed with the yum comming from pagefault.org, which also is newer. Pagefault's not so convenient because you have to use it from command line (type in yum list). But it works (for me). Editing yum.conf file to add a repository is a pain and i was not able to add other repository than pagefault (see links below). Also note, that Darrell's yum does not completely deinstalls itself via rpm -e.
More yummie: http://forums.contribs.org/index.php?topic=21205.0
http://forums.contribs.org/index.php?topic=21911.0
-
I have been using Darrell's yum (yum-1.0.3-6.0.7.x.esmith & smeserver-yum-1.0.0-03dmay)for a while and then it stopped working with the same error. I had only made one change which was to install Zope which required a later version of Python. So I uninstalled Zope & went back to python-1.5.2-43.73 and all OK. It appears that yum is very version specific for python. I re-installed python-2.2.1-17.i386.rpm and recompiled yum from source & upgraded but the error returned. Does anyone have any idea why this is so?
Cheers
Nic Baxter
-
Is Darrell May, by any chance, reading this? Charlie Brady pointed out in the bug forum to report errors directly to the contributer.