# Cannot update SLES 11 SP3

**URL:** <https://forums.suse.com/t/cannot-update-sles-11-sp3/27298>\
**Category:** SLES Updates\
**Created:** [August 4, 2015, 12:38am UTC](https://forums.suse.com/t/cannot-update-sles-11-sp3/27298 "2015-08-04T00:38:00Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jayvi](https://avatars.discourse-cdn.com/v4/letter/j/34f0e0/32.png) [@jayvi](https://forums.suse.com/u/jayvi)\
**Post date:** [August 4, 2015, 12:38am UTC](https://forums.suse.com/t/cannot-update-sles-11-sp3/27298/1 "2015-08-04T00:38:00Z")

</div>

I have been working with SLES since SP1 and I have not seen this issue before:

[CODE]# zypper --plus-repo dir:///data/appliance/updater/work/update.repo update --no-recommends sles-release  
Adding repository ‘dir:///data/appliance/updater/work/update.repo’ [done]  
Repository ‘dir:///data/appliance/updater/work/update.repo’ successfully added  
Enabled: Yes  
Autorefresh: Yes  
GPG check: Yes  
URI: dir:///data/appliance/updater/work/update.repo

Retrieving repository ‘dir:///data/appliance/updater/work/update.repo’ metadata [done]  
Building repository ‘dir:///data/appliance/updater/work/update.repo’ cache [done]  
Loading repository data…  
Reading installed packages…  
Resolving package dependencies…

Problem: product:SUSE\_SLES-11.3-1.138.x86\_64 requires sles-release = 11.3-1.138, but this requirement cannot be provided  
deleted providers: sles-release-11.3-1.138.x86\_64  
Solution 1: deinstallation of product:SUSE\_SLES-11.3-1.138.x86\_64  
Solution 2: do not install sles-release-11.3-1.201.x86\_64  
Solution 3: break product:SUSE\_SLES-11.3-1.138.x86\_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c] (c):[/CODE]

I’m not even sure what a product means to zypper. I guess I need to update my product first. How do I do that?

---

<div class="post-metadata">

**Author:** ![jayvi](https://avatars.discourse-cdn.com/v4/letter/j/34f0e0/32.png) [@jayvi](https://forums.suse.com/u/jayvi)\
**Post date:** [August 4, 2015, 2:28am UTC](https://forums.suse.com/t/cannot-update-sles-11-sp3/27298/2 "2015-08-04T02:28:19Z")

</div>

Some more information. We build our own zypper repository that contains packages from our SMT server and our own packages. I believe that we are missing meta-data in our zypper repository to trigger the product update.

---

<div class="post-metadata">

**Author:** ![jayvi](https://avatars.discourse-cdn.com/v4/letter/j/34f0e0/32.png) [@jayvi](https://forums.suse.com/u/jayvi)\
**Post date:** [August 5, 2015, 3:21am UTC](https://forums.suse.com/t/cannot-update-sles-11-sp3/27298/3 "2015-08-05T03:21:47Z")

</div>

After a day of meditating and reverse-engineering the metadata on our SLES11\_SP3\_Updates\_Repo, I was able to resolve this problem by using modifyrepo to install the products.xml.gz and updateinfo.xml.gz from SLES11\_SP3\_Updates\_Repo into our update repo. Our SLES appliances now update correctly.

---

<div class="post-metadata">

**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\
**Post date:** [August 5, 2015, 2:20pm UTC](https://forums.suse.com/t/cannot-update-sles-11-sp3/27298/4 "2015-08-05T14:20:45Z")

</div>

Hi jayvi,

thank you for reporting back your results - and congrats to solving the problem, since obviously no-one here was able to come up with suggestions in time :-[

Regards,  
Jens

---

<div class="post-metadata">

**Author:** ![mikenash](https://avatars.discourse-cdn.com/v4/letter/m/977dab/32.png) [@mikenash](https://forums.suse.com/u/mikenash)\
**Post date:** [August 11, 2015, 5:21pm UTC](https://forums.suse.com/t/cannot-update-sles-11-sp3/27298/5 "2015-08-11T17:21:28Z")

</div>

I resolved my metadata issue with the following procedure.  
Reference Document ID:7013434

1. Get the following files from the SLE 11 SP2 or SP3 Media (the iso or DVD that matches the version of your system):

The versions shown are for SLE 11 SP2 but the SP3 files are in the same location.  
libgpg-error0-1.10-0.7.29.s390x.rpm  
libgpg-error0-32bit-1.10-0.7.29.s390x.rpm  
suse-build-key-1.0-907.42.35.noarch.rpm

1. Copy them to the server and do the following:

rpm -Uvh libgpg-error0\*  
rpm -e --nodeps suse-build-key  
rpm -Uvh suse-build-key-1.0-907.42.35.noarch.rpm (replacing the SP3 version if necessary)

1. run zypper ref

---

<div class="post-metadata">

**Author:** ![GMZjflores](https://avatars.discourse-cdn.com/v4/letter/g/eada6e/32.png) [@GMZjflores](https://forums.suse.com/u/GMZjflores)\
**Post date:** [August 21, 2015, 3:44pm UTC](https://forums.suse.com/t/cannot-update-sles-11-sp3/27298/6 "2015-08-21T15:44:05Z")

</div>

> [@jayvi;29005](#):
>
> After a day of meditating and reverse-engineering the metadata on our SLES11\_SP3\_Updates\_Repo, I was able to resolve this problem by using modifyrepo to install the products.xml.gz and updateinfo.xml.gz from SLES11\_SP3\_Updates\_Repo into our update repo. Our SLES appliances now update correctly.

Hi Jayvi,

I ran into the same problem. Would you mind explaining how you got the products.xml and updateinfo.xml metadata into your repository?

Kind regards,  
Javier
