Koozali.org: home of the SME Server
Contribs.org Forums => Koozali SME Server 10.x Contribs => Topic started by: p1ur on October 24, 2022, 09:50:46 PM
-
From the software installer:
--> Running transaction check
---> Package libicu71.x86_64 0:71.1-2.el7.remi will be installed
--> Processing Conflict: e-smith-email-5.6.0-19.el7.sme.noarch conflicts smeserver-fetchmail < 1.6-24
--> Finished Dependency Resolution
--> Running transaction check
---> Package e-smith-email.noarch 0:5.6.0-17.el7.sme will be updated
---> Package e-smith-email.noarch 0:5.6.0-17.el7.sme will be updated
---> Package kernel.x86_64 0:3.10.0-1160.49.1.el7 will be erased
--> Processing Conflict: e-smith-email-5.6.0-19.el7.sme.noarch conflicts smeserver-fetchmail < 1.6-24
--> Finished Dependency Resolution
Error: e-smith-email conflicts with smeserver-fetchmail-1.6-22.el7.sme.noarch
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
yum update bglibs.x86_64 [Removed list of updates except first and last…] tzdata.noarch failed: 256
The system needs to be reconfigured after adding or removing software, or applying updates.
Please click on the Reconfigure button at the bottom of this page to start the reconfiguration process. An automatic reboot will be initiated as part of this reconfiguration process
I have NOT clicked on the reconfigure button.
From the config report:
==================
Base configuration
==================
SME server version: 10.0
SME server mode: servergateway
SME server previous mode: servergateway
Running Kernel: 3.10.0-1160.71.1.el7.x86_64
What is next step?
Regards
p1ur
-
You probably have smecontribs repo disabled
Update smeserver-fetchmail from smecontribs from the terminal:
yum --enablerepo=smecontribs install smeserver-fetchmail
You can set the smecontribs repo permanently enabled (which I think is the new default going forward)
db yum_repositories setprop smecontribs status enabled
signal-event yum-modify
-
Thats it. The smecontribs was disabled.
From the configreport:
=======================
Additional repositories
=======================
base: enabled
centosplus: disabled
extras: disabled
fasttrack: disabled
remi-safe: enabled
smeaddons: enabled
smecontribs: disabled
smedev: disabled
smeextras: enabled
smeos: enabled
smetest: disabled
smeupdates: enabled
smeupdates-testing: disabled
updates: enabled
I have permanently enabled smecontribs repo:
db yum_repositories setprop smecontribs status enabled
signal-event yum-modify
And the [Software installer] is running.
Thanks p1ur
-
Cool.
I *think* that we are changing the default but can't remember the status - I need to ask JP.
Good that it gets you going.
-
Not enabled by default on update of existing install (in my experience).
-
Not enabled by default on update of existing install (in my experience).
Yes I think this is 'In Progress'. It may be enabled in a new install but I haven't tested that - Terry will know. It would need a migrate script for older installs.
Unless you have a specific reason not too then you can enable the repo by default.
-
Yes I think this is 'In Progress'. It may be enabled in a new install but I haven't tested that - Terry will know. It would need a migrate script for older installs.
ahhhh, on a clean install
[root@sme111 ~]# db yum_repositories show smecontribs
smecontribs=repository
EnableGroups=yes
GPGCheck=yes
MirrorList=https://mirrorlist.koozali.org/mirrorlist/smecontribs-10
Name=SME Server - contribs
Visible=yes
status=disabled
[root@sme111 ~]# db yum_repositories setprop smecontribs status enabled
[root@sme111 ~]# db yum_repositories show smecontribs
smecontribs=repository
EnableGroups=yes
GPGCheck=yes
MirrorList=https://mirrorlist.koozali.org/mirrorlist/smecontribs-10
Name=SME Server - contribs
Visible=yes
status=enabled
-
Ok, so he still hasn't done it which means this is a bug I guess.
-
Ok, so he still hasn't done it which means this is a bug I guess.
This VM has not been updated either, so maybe in an update
-
Here's what I see for defaults on my up-to-date SME10.1 server:
./base/status:enabled
./remi-safe/status:enabled
./smeaddons/status:enabled
./smeextras/status:enabled
./smeos/status:enabled
./smeupdates/status:enabled
./updates/status:enabled
./centosplus/status:disabled
./extras/status:disabled
./fasttrack/status:disabled
./smecontribs/status:disabled
./smedev/status:disabled
./smetest/status:disabled
./smeupdates-testing/status:disabled
./node10/status:disabled
./node11/status:disabled
./node12/status:disabled
./node13/status:disabled
./node14/status:disabled
./node15/status:disabled
./node16/status:disabled
./node17/status:disabled
./node4/status:disabled
./node5/status:disabled
./node6/status:disabled
./node7/status:disabled
./node8/status:disabled
./node9/status:disabled
[edit]
The wiki includes instructions for resetting yum repositories to the SME defaults (added to this post as as a reference...)
cd /home/e-smith/db/
mv yum_repositories yum_repositories.po
/etc/e-smith/events/actions/initialize-default-databases
-
I think it is a point JP mentioned.
If not enabled it can cause a bug as above.
JP is on a well deserved break right now and back in a while.
Sure he'll respond accordingly in due course.
-
it needs to be enabled as soon as you use a contrib.
it should be enabled as default, and i think we forgot to do it on last release and should be fixed for next new installs.
on existing it is hard to do anything as we do not want to go against to those who absolutely want to have it disabled.
-
on existing it is hard to do anything as we do not want to go against to those who absolutely want to have it disabled.
... and I love SME for this philosophy... ^_^