Koozali.org: home of the SME Server

Update throwing up error?

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: Update throwing up error?
« Reply #15 on: November 07, 2018, 06:25:57 PM »
The supposed dependency on Apache::Test is bogus:

charlieb@localhost:~/Downloads/spamassassin $ rpm2cpio spamassassin-3.4.1-1.el6.sme.x86_64.rpm | cpio -id
8046 blocks
charlieb@localhost:~/Downloads/spamassassin $ grep -r Apache::Test .
Binary file ./spamassassin-3.4.1-1.el6.sme.x86_64.rpm matches
charlieb@localhost:~/Downloads/spamassassin $ ls
etc  spamassassin-3.4.1-1.el6.sme.x86_64.rpm  usr  var
charlieb@localhost:~/Downloads/spamassassin $

However, I don't think that matters. I can see the smeupdates repo contains a newer mod_perl rpm which doesn't contain those conflicting files, so wouldn't require you to remove perl-Apache-Test:

charlieb@localhost:~/Downloads $ rpm -qlp mod_perl-2.0.4-12.1.el6.sme.x86_64.rpm | grep Apache::
warning: mod_perl-2.0.4-12.1.el6.sme.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 1e9c9308: NOKEY
charlieb@localhost:~/Downloads $

Offline Drifting

  • ****
  • 431
  • +0/-0
Re: Update throwing up error?
« Reply #16 on: November 25, 2018, 02:04:04 PM »
Sorry for my Tardy response, poor wifey was in hospital, and this was the least of my problems.

Have I misunderstood that this is fixed? or was there something else I was expected to do to cure this? Totally lost the train of thought, sorry :-(

Paul

[root@ins1 ~]# db yum_repositories setprop smeupdates status enabled
[root@ins1 ~]# yum update
Loaded plugins: fastestmirror, smeserver
Setting up Update Process
Loading mirror speeds from cached hostfile
 * base: mirrors.coreix.net
 * smeaddons: mirror.pialasse.com
 * smeextras: mirror.pialasse.com
 * smeos: mirror.pialasse.com
 * updates: mirror.freethought-internet.co.uk
Resolving Dependencies
--> Running transaction check
---> Package device-mapper-multipath.x86_64 0:0.4.9-106.el6 will be updated
---> Package device-mapper-multipath.x86_64 0:0.4.9-106.el6_10.1 will be an update
---> Package device-mapper-multipath-libs.x86_64 0:0.4.9-106.el6 will be updated
---> Package device-mapper-multipath-libs.x86_64 0:0.4.9-106.el6_10.1 will be an update
---> Package dhclient.x86_64 12:4.1.1-61.P1.el6.centos will be updated
---> Package dhclient.x86_64 12:4.1.1-63.P1.el6.centos will be an update
---> Package dhcp.x86_64 12:4.1.1-61.P1.el6.centos will be updated
---> Package dhcp.x86_64 12:4.1.1-63.P1.el6.centos will be an update
---> Package dhcp-common.x86_64 12:4.1.1-61.P1.el6.centos will be updated
---> Package dhcp-common.x86_64 12:4.1.1-63.P1.el6.centos will be an update
---> Package kernel.x86_64 0:2.6.32-754.6.3.el6 will be installed
---> Package kernel-firmware.noarch 0:2.6.32-754.3.5.el6 will be updated
---> Package kernel-firmware.noarch 0:2.6.32-754.6.3.el6 will be an update
---> Package kernel-headers.x86_64 0:2.6.32-754.3.5.el6 will be updated
---> Package kernel-headers.x86_64 0:2.6.32-754.6.3.el6 will be an update
---> Package kpartx.x86_64 0:0.4.9-106.el6 will be updated
---> Package kpartx.x86_64 0:0.4.9-106.el6_10.1 will be an update
---> Package mailx.x86_64 0:12.4-8.el6_6 will be updated
---> Package mailx.x86_64 0:12.4-10.el6_10 will be an update
---> Package mod_perl.x86_64 0:2.0.4-11.1.el6.sme will be updated
---> Package mod_perl.x86_64 0:2.0.4-12.el6_10 will be an update
---> Package nfs-utils.x86_64 1:1.2.3-78.el6 will be updated
---> Package nfs-utils.x86_64 1:1.2.3-78.el6_10.1 will be an update
---> Package nss.x86_64 0:3.36.0-8.el6 will be updated
---> Package nss.x86_64 0:3.36.0-9.el6_10 will be an update
---> Package nss-sysinit.x86_64 0:3.36.0-8.el6 will be updated
---> Package nss-sysinit.x86_64 0:3.36.0-9.el6_10 will be an update
---> Package nss-tools.x86_64 0:3.36.0-8.el6 will be updated
---> Package nss-tools.x86_64 0:3.36.0-9.el6_10 will be an update
---> Package tzdata.noarch 0:2018e-3.el6 will be updated
---> Package tzdata.noarch 0:2018g-1.el6 will be an update
---> Package yum.noarch 0:3.2.29-81.el6.centos will be updated
---> Package yum.noarch 0:3.2.29-81.el6.centos.0.1 will be an update
--> Finished Dependency Resolution
--> Running transaction check
---> Package kernel.x86_64 0:2.6.32-696.30.1.el6 will be erased
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package                      Arch   Version                     Repository
                                                                           Size
================================================================================
Installing:
 kernel                       x86_64 2.6.32-754.6.3.el6          updates   32 M
Updating:
 device-mapper-multipath      x86_64 0.4.9-106.el6_10.1          updates  133 k
 device-mapper-multipath-libs x86_64 0.4.9-106.el6_10.1          updates  204 k
 dhclient                     x86_64 12:4.1.1-63.P1.el6.centos   updates  323 k
 dhcp                         x86_64 12:4.1.1-63.P1.el6.centos   updates  824 k
 dhcp-common                  x86_64 12:4.1.1-63.P1.el6.centos   updates  145 k
 kernel-firmware              noarch 2.6.32-754.6.3.el6          updates   29 M
 kernel-headers               x86_64 2.6.32-754.6.3.el6          updates  4.5 M
 kpartx                       x86_64 0.4.9-106.el6_10.1          updates   72 k
 mailx                        x86_64 12.4-10.el6_10              updates  235 k
 mod_perl                     x86_64 2.0.4-12.el6_10             updates  3.2 M
 nfs-utils                    x86_64 1:1.2.3-78.el6_10.1         updates  337 k
 nss                          x86_64 3.36.0-9.el6_10             updates  865 k
 nss-sysinit                  x86_64 3.36.0-9.el6_10             updates   53 k
 nss-tools                    x86_64 3.36.0-9.el6_10             updates  460 k
 tzdata                       noarch 2018g-1.el6                 updates  498 k
 yum                          noarch 3.2.29-81.el6.centos.0.1    updates  1.0 M
Removing:
 kernel                       x86_64 2.6.32-696.30.1.el6         @updates 133 M

Transaction Summary
================================================================================
Install       1 Package(s)
Upgrade      16 Package(s)
Remove        1 Package(s)

Total size: 74 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test


Transaction Check Error:
  file /usr/share/man/man3/Apache::Test.3pm.gz from install of mod_perl-2.0.4-12.el6_10.x86_64 conflicts with file from package perl-Apache-Test-1.30-2.el6.rf.noarch
  file /usr/share/man/man3/Apache::TestConfig.3pm.gz from install of mod_perl-2.0.4-12.el6_10.x86_64 conflicts with file from package perl-Apache-Test-1.30-2.el6.rf.noarch
  file /usr/share/man/man3/Apache::TestMB.3pm.gz from install of mod_perl-2.0.4-12.el6_10.x86_64 conflicts with file from package perl-Apache-Test-1.30-2.el6.rf.noarch
  file /usr/share/man/man3/Apache::TestMM.3pm.gz from install of mod_perl-2.0.4-12.el6_10.x86_64 conflicts with file from package perl-Apache-Test-1.30-2.el6.rf.noarch
  file /usr/share/man/man3/Apache::TestReport.3pm.gz from install of mod_perl-2.0.4-12.el6_10.x86_64 conflicts with file from package perl-Apache-Test-1.30-2.el6.rf.noarch
  file /usr/share/man/man3/Apache::TestRequest.3pm.gz from install of mod_perl-2.0.4-12.el6_10.x86_64 conflicts with file from package perl-Apache-Test-1.30-2.el6.rf.noarch
  file /usr/share/man/man3/Apache::TestRun.3pm.gz from install of mod_perl-2.0.4-12.el6_10.x86_64 conflicts with file from package perl-Apache-Test-1.30-2.el6.rf.noarch
  file /usr/share/man/man3/Apache::TestRunPHP.3pm.gz from install of mod_perl-2.0.4-12.el6_10.x86_64 conflicts with file from package perl-Apache-Test-1.30-2.el6.rf.noarch
  file /usr/share/man/man3/Apache::TestRunPerl.3pm.gz from install of mod_perl-2.0.4-12.el6_10.x86_64 conflicts with file from package perl-Apache-Test-1.30-2.el6.rf.noarch
  file /usr/share/man/man3/Apache::TestServer.3pm.gz from install of mod_perl-2.0.4-12.el6_10.x86_64 conflicts with file from package perl-Apache-Test-1.30-2.el6.rf.noarch
  file /usr/share/man/man3/Apache::TestSmoke.3pm.gz from install of mod_perl-2.0.4-12.el6_10.x86_64 conflicts with file from package perl-Apache-Test-1.30-2.el6.rf.noarch
  file /usr/share/man/man3/Apache::TestTrace.3pm.gz from install of mod_perl-2.0.4-12.el6_10.x86_64 conflicts with file from package perl-Apache-Test-1.30-2.el6.rf.noarch
  file /usr/share/man/man3/Apache::TestUtil.3pm.gz from install of mod_perl-2.0.4-12.el6_10.x86_64 conflicts with file from package perl-Apache-Test-1.30-2.el6.rf.noarch
Infamy, Infamy, they all have it in for me!

Offline TerryF

  • grumpy old man
  • *
  • 1,826
  • +6/-0
Re: Update throwing up error?
« Reply #17 on: November 25, 2018, 02:26:43 PM »
Have I misunderstood that this is fixed? or was there something else I was expected to do to cure this? Totally lost the train of thought, sorry :-(

Paul

[root@ins1 ~]# db yum_repositories setprop smeupdates status enabled
[root@ins1 ~]# yum update
Loaded plugins: fastestmirror, smeserver
Setting up Update Process
Loading mirror speeds from cached hostfile
 * base: mirrors.coreix.net
 * smeaddons: mirror.pialasse.com
 * smeextras: mirror.pialasse.com
 * smeos: mirror.pialasse.com
 * updates: mirror.freethought-internet.co.uk
Resolving Dependencies
--> Running transaction check

You are still not pulling from smeupdates, that is where the package is..

As I in previous post...

First #  /sbin/e-smith/audittools/repositories

to make sure you actually have smeupdates configured

My repos

[root@fagehome ~]#  /sbin/e-smith/audittools/repositories
atrpms: disabled
atrpms-testing: disabled
base: enabled
centosplus: disabled
contrib: disabled
dag: disabled
epel: disabled
extras: disabled
fasttrack: disabled
fws: disabled
fws-testing: disabled
openfusion: disabled
reetp: disabled
remi-safe: enabled
rpmforge: disabled
rpmfusion: disabled
sme7contribs: disabled
smeaddons: enabled
smecontribs: enabled
smedev: disabled
smeextras: enabled
smeos: enabled
smetest: disabled
smeupdates: enabled
smeupdates-testing: disabled
stephdl: disabled
updates: enabled

then

Make sure that smeupdates is present if it is but disabled then

# db yum_repositories setprop smeupdates status enabled

then (didn't show this in last post)

# signal-event yum-modify

and run

# yum update..

If smeupdates is not listed then you will have to add it back
https://wiki.contribs.org/SME_Server:Adding_Software#Restoring_Default_Yum_Repositories
--
qui scribit bis legit

Offline Drifting

  • ****
  • 431
  • +0/-0
Re: Update throwing up error?
« Reply #18 on: November 25, 2018, 03:00:16 PM »
You are still not pulling from smeupdates, that is where the package is..

As I in previous post...

First #  /sbin/e-smith/audittools/repositories

to make sure you actually have smeupdates configured

My repos

[root@fagehome ~]#  /sbin/e-smith/audittools/repositories
atrpms: disabled
atrpms-testing: disabled
base: enabled
centosplus: disabled
contrib: disabled
dag: disabled
epel: disabled
extras: disabled
fasttrack: disabled
fws: disabled
fws-testing: disabled
openfusion: disabled
reetp: disabled
remi-safe: enabled
rpmforge: disabled
rpmfusion: disabled
sme7contribs: disabled
smeaddons: enabled
smecontribs: enabled
smedev: disabled
smeextras: enabled
smeos: enabled
smetest: disabled
smeupdates: enabled
smeupdates-testing: disabled
stephdl: disabled
updates: enabled

then

Make sure that smeupdates is present if it is but disabled then

# db yum_repositories setprop smeupdates status enabled

then (didn't show this in last post)

# signal-event yum-modify

and run

# yum update..

If smeupdates is not listed then you will have to add it back
https://wiki.contribs.org/SME_Server:Adding_Software#Restoring_Default_Yum_Repositories

Well that was odd, it was actually there! I did follow your earlier instructions. Did a signal-event etc, tried again and it has worked! Brilliant thank you all for the help.

Regards Paul
« Last Edit: November 25, 2018, 03:05:23 PM by Drifting »
Infamy, Infamy, they all have it in for me!

Offline TerryF

  • grumpy old man
  • *
  • 1,826
  • +6/-0
Re: Update throwing up error?
« Reply #19 on: November 25, 2018, 09:17:35 PM »
No worries mate :-) my fault by omission, not including the # signal-event yum-modify
the first time round..
--
qui scribit bis legit