# Locking package(s) that cause(s) patch dependency conflict

**URL:** <https://forums.suse.com/t/locking-package-s-that-cause-s-patch-dependency-conflict/22042>\
**Category:** SLES Updates\
**Created:** [January 18, 2012, 11:06pm UTC](https://forums.suse.com/t/locking-package-s-that-cause-s-patch-dependency-conflict/22042 "2012-01-18T23:06:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![System1](https://avatars.discourse-cdn.com/v4/letter/s/51bf81/32.png) [@System1](https://forums.suse.com/u/System1)\
**Post date:** [January 18, 2012, 11:06pm UTC](https://forums.suse.com/t/locking-package-s-that-cause-s-patch-dependency-conflict/22042/1 "2012-01-18T23:06:02Z")

</div>

I haven’t worked with package locking/protecting using either zypper or  
Yast2 Online Update before so please excuse me if this is an easy  
question.

I needed to install the PHP OCI8 extension. This required php5-devel  
which is available on the SLES 11 SP1 SDK DVD. This is not the newest  
version of php5-devel, but it’s the newest version provided by Novell,  
and I like to use Novell-provided packages whenever possible.  
Installing php5-devel from the SDK DVD required the downgrade of 15  
dependencies. See the Yast2 conflicts list below.  
[color=blue]

> php5-devel-5.2.6-50.24.1.x86\_64 requires php5 = 5.2.6, but this  
> requirement cannot be provided  
> uninstallable providers:  
> php5-5.2.6-50.24.1.x86\_64[SUSE-Linux-Enterprise-Software-Development-Kit-11-SP1\_11.1.1-1.57]
> 
> php5-5.2.6-50.24.1.x86\_64[nu\_novell\_com:SLES11-SP1-Pool]  
> Following actions will be done:  
> downgrade of php5-5.2.14-0.7.24.1.x86\_64 to php5-5.2.6-50.24.1.x86\_64  
> downgrade of php5-mysql-5.2.14-0.7.24.1.x86\_64 to  
> php5-mysql-5.2.6-50.24.1.x86\_64  
> downgrade of php5-tokenizer-5.2.14-0.7.24.1.x86\_64 to  
> php5-tokenizer-5.2.6-50.24.1.x86\_64  
> downgrade of php5-iconv-5.2.14-0.7.24.1.x86\_64 to  
> php5-iconv-5.2.6-50.24.1.x86\_64  
> downgrade of php5-ctype-5.2.14-0.7.24.1.x86\_64 to  
> php5-ctype-5.2.6-50.24.1.x86\_64  
> downgrade of php5-suhosin-5.2.14-0.7.24.1.x86\_64 to  
> php5-suhosin-5.2.6-50.24.1.x86\_64  
> downgrade of php5-zip-5.2.14-0.7.24.1.x86\_64 to  
> php5-zip-5.2.6-50.24.1.x86\_64  
> downgrade of php5-dom-5.2.14-0.7.24.1.x86\_64 to  
> php5-dom-5.2.6-50.24.1.x86\_64  
> downgrade of php5-mbstring-5.2.14-0.7.24.1.x86\_64 to  
> php5-mbstring-5.2.6-50.24.1.x86\_64  
> downgrade of php5-xmlreader-5.2.14-0.7.24.1.x86\_64 to  
> php5-xmlreader-5.2.6-50.24.1.x86\_64  
> downgrade of php5-xmlwriter-5.2.14-0.7.24.1.x86\_64 to  
> php5-xmlwriter-5.2.6-50.24.1.x86\_64  
> downgrade of php5-pdo-5.2.14-0.7.24.1.x86\_64 to  
> php5-pdo-5.2.6-50.24.1.x86\_64  
> downgrade of php5-hash-5.2.14-0.7.24.1.x86\_64 to  
> php5-hash-5.2.6-50.24.1.x86\_64  
> downgrade of php5-json-5.2.14-0.7.24.1.x86\_64 to  
> php5-json-5.2.6-50.24.1.x86\_64  
> downgrade of apache2-mod\_php5-5.2.14-0.7.24.1.x86\_64 to  
> apache2-mod\_php5-5.2.6-50.24.1.x86\_64[/color]

Now that the dependencies have been downgraded and the php5-devel  
package has been installed, whenever I open Yast2 Online Update, I get  
the following message.  
[color=blue]

> php5-sqlite-5.2.6-50.24.1.x86\_64 requires php5-pdo = 5.2.6, but this  
> requirement cannot be provided
> 
> Following actions will be done:  
> deinstallation of php5-sqlite-5.2.6-50.24.1.x86\_64  
> deinstallation of php5-devel-5.2.6-50.24.1.x86\_64  
> do not install patch:slessp1-apache2-mod\_php5-4663.noarch
> 
> break php5-sqlite by ignoring some of its dependencies[/color]

I have been choosing option 2 (“do not install  
patch:slessp1-apache2-mod\_php5-4663.noarch”) but I am wondering if  
there’s an easy way to lock the proper files so that I can continue  
upgrading using Yast2 Online Update or “zypper update” without worrying  
that I’ll upgrade the wrong packages and break PHP’s OCI8 extension.  
There’s no way to lock “patch:slessp1-apache2-mod\_php5-4663.noarch” that  
I know about, so would I simply lock the 15 packages that had to be  
downgraded? Should I also lock php5-sqlite since that seems to be the  
package requesting the upgrade of php5-pdo?

Any help/explanations would be greatly appreciated.

Thanks.  
Dan

## – dcaunt

dcaunt’s Profile: [http://forums.novell.com/member.php?userid=73309](http://forums.novell.com/member.php?userid=73309)  
View this thread: [http://forums.novell.com/showthread.php?t=450999](http://forums.novell.com/showthread.php?t=450999)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\
**Post date:** [January 23, 2012, 2:16pm UTC](https://forums.suse.com/t/locking-package-s-that-cause-s-patch-dependency-conflict/22042/2 "2012-01-23T14:16:02Z")

</div>

Novell also provides updates to the php5 SDK packages. if you properly  
installed the SDK CD as an addon, you actually should get it  
automatically. if you did not and don’t want to bother with it, you can  
also go to ‘NOVELL: Patch Finder’  
([http://download.novell.com/patch/finder](http://download.novell.com/patch/finder)) and download the individual  
packages that you need (although that is discouraged, as you will end up  
with the same problem later again).

-_zypper\_patch_- will always update to the lastest recommended packages  
from Novell, so even if you’d add a lock, you would get the same  
conflict message everytime. We do encourage you to switch to the latest  
update.

## – dirkmueller

dirkmueller’s Profile: [http://forums.novell.com/member.php?userid=21451](http://forums.novell.com/member.php?userid=21451)  
View this thread: [http://forums.novell.com/showthread.php?t=450999](http://forums.novell.com/showthread.php?t=450999)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\
**Post date:** [January 24, 2012, 7:46pm UTC](https://forums.suse.com/t/locking-package-s-that-cause-s-patch-dependency-conflict/22042/3 "2012-01-24T19:46:02Z")

</div>

dirkmueller;2169825 Wrote:[color=blue]

> Novell also provides updates to the php5 SDK packages. if you properly  
> installed the SDK CD as an addon, you actually should get it  
> automatically. if you did not and don’t want to bother with it, you can  
> also go to ‘NOVELL: Patch Finder’  
> ([http://download.novell.com/patch/finder](http://download.novell.com/patch/finder)) and download the individual  
> packages that you need (although that is discouraged, as you will end up  
> with the same problem later again).
> 
> -_zypper\_patch_- will always update to the lastest recommended packages  
> from Novell, so even if you’d add a lock, you would get the same  
> conflict message everytime. We do encourage you to switch to the latest  
> update.[/color]

Thanks, dirkmueller. I did find the latest php5-devel (5.2.14) in the  
Novell Patch Finder. However, it seems it would be easier if I could  
get the Add On installed correctly. But, even after using the “Add On  
Products” feature in Yast to add the SDK DVD, when I run Online Update  
it still doesn’t show me the latest version of php5-devel that was on  
Novell Patch Finder. It only shows the version on the SDK DVD. Is  
there something else I must check before Online Update will show me the  
patches from the Add On for the SDK packages? Or is there another  
program I should be using to update “add on” packages?

## – dcaunt

dcaunt’s Profile: [http://forums.novell.com/member.php?userid=73309](http://forums.novell.com/member.php?userid=73309)  
View this thread: [http://forums.novell.com/showthread.php?t=450999](http://forums.novell.com/showthread.php?t=450999)
