Bug 1145821 - Updated version of php53-mapi-7.1.10-4.el5.x86_64.rpm missing (i386 also)
Summary: Updated version of php53-mapi-7.1.10-4.el5.x86_64.rpm missing (i386 also)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: php53-mapi
Version: el5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robert Scheck
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-23 21:05 UTC by Daniel Fiederling
Modified: 2014-10-09 19:58 UTC (History)
1 user (show)

Fixed In Version: php53-mapi-7.1.10-4.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-25 18:31:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Daniel Fiederling 2014-09-23 21:05:53 UTC
EPEL currently contains version 7.1.10-4 of Zarafa but only php53-mapi-7.1.10-2.el5.x86_64.rpm.

Updating Zarafa by yum on CentOS/RHEL 5.10 fails because yum tries to resolve the dependency with php-mapi-7-1.10-4 which fails on systems that only use php53 packages:

# yum update
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package libmapi.x86_64 0:7.1.10-4.el5 set to be updated
---> Package python-MAPI.x86_64 0:7.1.10-4.el5 set to be updated
---> Package zarafa.x86_64 0:7.1.10-4.el5 set to be updated
---> Package zarafa-client.x86_64 0:7.1.10-4.el5 set to be updated
---> Package zarafa-common.x86_64 0:7.1.10-4.el5 set to be updated
---> Package zarafa-contacts.x86_64 0:7.1.10-4.el5 set to be updated
---> Package zarafa-dagent.x86_64 0:7.1.10-4.el5 set to be updated
--> Processing Dependency: php-mapi = 7.1.10-4.el5 for package: zarafa-dagent
---> Package zarafa-gateway.x86_64 0:7.1.10-4.el5 set to be updated
---> Package zarafa-ical.x86_64 0:7.1.10-4.el5 set to be updated
---> Package zarafa-monitor.x86_64 0:7.1.10-4.el5 set to be updated
---> Package zarafa-search.x86_64 0:7.1.10-4.el5 set to be updated
---> Package zarafa-server.x86_64 0:7.1.10-4.el5 set to be updated
---> Package zarafa-spooler.x86_64 0:7.1.10-4.el5 set to be updated
---> Package zarafa-utils.x86_64 0:7.1.10-4.el5 set to be updated
---> Package zarafa-webaccess.x86_64 0:7.1.10-4.el5 set to be updated
--> Running transaction check
---> Package php-mapi.x86_64 0:7.1.10-4.el5 set to be updated
--> Processing Dependency: php-api = 20041225 for package: php-mapi
--> Running transaction check
---> Package php-common.x86_64 0:5.1.6-44.el5_10 set to be updated
--> Processing Conflict: php53-common conflicts php-common
--> Finished Dependency Resolution
php53-common-5.3.3-23.el5_10.x86_64 from installed has depsolving problems
  --> php53-common conflicts with php-common
Error: php53-common conflicts with php-common
 You could try using --skip-broken to work around the problem
 You could try running: package-cleanup --problems
                        package-cleanup --dupes
                        rpm -Va --nofiles --nodigest



Please provide updates php53-mapi packages.

Comment 1 Fedora Update System 2014-09-23 22:20:17 UTC
php53-mapi-7.1.10-4.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/php53-mapi-7.1.10-4.el5

Comment 2 Fedora Update System 2014-09-25 00:16:58 UTC
Package php53-mapi-7.1.10-4.el5:
* should fix your issue,
* was pushed to the Fedora EPEL 5 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing php53-mapi-7.1.10-4.el5'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2792/php53-mapi-7.1.10-4.el5
then log in and leave karma (feedback).

Comment 3 Daniel Fiederling 2014-09-25 18:31:32 UTC
Updated packages in EPEL testing fixed the update issue.
Thank you!

Comment 4 Fedora Update System 2014-10-09 19:58:50 UTC
php53-mapi-7.1.10-4.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.