Topic: Trouble with yum update

[jumba]

Hi all!

On a SME Server 7.5.1 with all updates installed, "something happened" during an update in late December (as far as I can understand, due to a suddeen power failure)

Well, after this the server sends the following mail:

Code: [Select]

===
=== yum reports available updates:
===

e-smith-devtools.noarch                  2.0.0-2.el4.sme        smeupdates     
e-smith-horde.noarch                     4.0.0-10.el4.sme       smeupdates     
e-smith-php.noarch                       2.0.0-2.el4.sme        smeupdates     
horde.noarch                             3.3.10-1.el4.sme       smeupdates     
perl-Compress-Raw-Bzip2.i386             2.031-1.el4.rf         smeupdates     
perl-Compress-Raw-Zlib.i386              2.030-1.el4.rf         smeupdates     
php.i386                                 4.3.9-3.31             updates   
...so accessing the server in order to fix this, I encounter the following situation:

Code: [Select]

# yum update
Loading "protect-packages" plugin
Loading "fastestmirror" plugin
Loading "smeserver" plugin
Loading "installonlyn" plugin
Setting up Update Process
Setting up repositories
smeaddons                 100% |=========================| 1.9 kB    00:00     
smeextras                 100% |=========================| 1.9 kB    00:00     
base                      100% |=========================| 1.1 kB    00:00     
updates                   100% |=========================|  951 B    00:00     
smeos                     100% |=========================| 1.9 kB    00:00     
smeupdates                100% |=========================| 1.9 kB    00:00     
Loading mirror speeds from cached hostfile
Reading repository metadata in from local files
Excluding Packages from CentOS - os
Finished
Excluding Packages from CentOS - updates
Finished
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package perl-Compress-Raw-Zlib.i386 0:2.030-1.el4.rf set to be updated
---> Package e-smith-php.noarch 0:2.0.0-2.el4.sme set to be updated
---> Package e-smith-devtools.noarch 0:2.0.0-2.el4.sme set to be updated
---> Package e-smith-horde.noarch 0:4.0.0-10.el4.sme set to be updated
---> Package perl-Compress-Raw-Bzip2.i386 0:2.031-1.el4.rf set to be updated
---> Package horde.noarch 0:3.3.10-1.el4.sme set to be updated
---> Package php.i386 0:4.3.9-3.31 set to be updated
--> Running transaction check
--> Processing Dependency: php = 4.3.9-3.29 for package: php-pear
--> Processing Dependency: php = 4.3.9-3.29 for package: php-ldap
--> Processing Dependency: php = 4.3.9-3.29 for package: php-mysql
--> Processing Dependency: php = 4.3.9-3.29 for package: php-mbstring
--> Processing Dependency: php = 4.3.9-3.29 for package: php-imap
--> Processing Dependency: php = 4.3.9-3.29 for package: php-gd
--> Finished Dependency Resolution
Error: Missing Dependency: php = 4.3.9-3.29 is needed by package php-pear
Error: Missing Dependency: php = 4.3.9-3.29 is needed by package php-ldap
Error: Missing Dependency: php = 4.3.9-3.29 is needed by package php-mysql
Error: Missing Dependency: php = 4.3.9-3.29 is needed by package php-mbstring
Error: Missing Dependency: php = 4.3.9-3.29 is needed by package php-imap
Error: Missing Dependency: php = 4.3.9-3.29 is needed by package php-gd


Now, how should I resolve this????

Many thanks for any input 

[byte]

Hi Jumba,

Could you please report any bugs and potential bugs in the bug tracker.

Thanks.

[jumba]

Thank you Byte, done:

http://bugs.contribs.org/show_bug.cgi?id=6488

[Stefano]

I had the same issue updating a server via remote ssh access.. connection died and yum did not complete the update

you have to manually remove the "old" php rpms and then reinstall the newer ones with yum

in my case I did:

Code: [Select]

rpm -e --nodeps `rpm -qa 2>/dev/null| grep 4.3.9-3.29 `
yum install php php-domxml php-gd php-imap php-ldap php-mbstring php-mysql php-pear

NOTE: YMMV, be carefull

[CharlieBrady]

I had the same issue updating a server via remote ssh access.. connection died and yum did not complete the update

Stefano, please provide your diagnosis and followup instructions via the bug tracker, rather than here.

Thanks.