# Not able to upgrade self built packages

**URL:** <https://forums.suse.com/t/not-able-to-upgrade-self-built-packages/22022>\
**Category:** SLES Updates\
**Created:** [December 5, 2011, 12:06pm UTC](https://forums.suse.com/t/not-able-to-upgrade-self-built-packages/22022 "2011-12-05T12:06:02Z")\
**Posts on this page:** 8\
**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:** [December 5, 2011, 12:06pm UTC](https://forums.suse.com/t/not-able-to-upgrade-self-built-packages/22022/1 "2011-12-05T12:06:02Z")

</div>

Hi all,

I’m experiencing some problems upgrading self built packages. This is  
mostly packages that are used for installing and configuring software.

If I run zypper lu, I can see that there are a available upgrade of  
this package:

## Code:

## v | self-x86\_64 | zypper-locks | 1-3 | 1-4 | noarch

If i run zypper up zypper-locks i get the following message back:

## Code:

~# zypper up zypper-locks  
Refreshing service ‘spacewalk’.  
Loading repository data…  
Reading installed packages…  
Resolving package dependencies…

Nothing to do.

* * *

If I try to upgrade one of the packages provided by Novell, it works:

## Code:

# zypper up sysstat

Refreshing service ‘spacewalk’.  
Loading repository data…  
Reading installed packages…  
Resolving package dependencies…

The following package is going to be upgraded:  
sysstat

The following package is not supported by its vendor:  
sysstat

1 package to upgrade.  
Overall download size: 173.0 KiB. After the operation, 638.0 KiB will be freed.  
Continue? [y/n/?] (y):

* * *

There are no conflicts that I can see, and if i run zypper up (no  
specific package spesified) the self built package is upgraded, and if i  
run zypper in -f zypper-locks that package is installed with the latest  
version…

That packages are built on a SLES11SP1 system and installed on a  
SLES11SP1 system. Packages are rebuilt with rpmbuild -bb package.spec.  
Not sure if this matters.

Could this be related to how the packages are built? Has anyone else  
seen this problem?

Thanks,

Alexander

## – alexanderdav

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

---

<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:** [December 5, 2011, 3:32pm UTC](https://forums.suse.com/t/not-able-to-upgrade-self-built-packages/22022/2 "2011-12-05T15:32:37Z")

</div>

On 05/12/2011 10:06, alexanderdav wrote:  
[color=blue]

> If i run zypper up zypper-locks i get the following message back:[/color]

What happens if you run “zypper in zypper-locks”?

## HTH.

Simon  
Novell Knowledge Partner (NKP)

* * *

## Do you work with Novell technologies at a university, college or school? If so, your campus could benefit from joining the Novell Technology Transfer Partner (TTP) program. See [novell.com/ttp](http://novell.com/ttp) for more details.

---

<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:** [December 5, 2011, 5:36pm UTC](https://forums.suse.com/t/not-able-to-upgrade-self-built-packages/22022/3 "2011-12-05T17:36:02Z")

</div>

Hi Simon,

Thanks for your answer.

When running zypper in zypper-locks, zypper tells me that the package  
is already installed:

## Code:

# zypper in zypper-locks

Refreshing service ‘spacewalk’.  
Loading repository data…  
Reading installed packages…  
‘zypper-locks’ is already installed.  
Resolving package dependencies…

## Nothing to do.

It looks like it does not register the update somehow, when running  
install or upgrade direct on the package…

## – alexanderdav

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

---

<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:** [December 6, 2011, 6:25am UTC](https://forums.suse.com/t/not-able-to-upgrade-self-built-packages/22022/4 "2011-12-06T06:25:00Z")

</div>

On Mon, 05 Dec 2011 15:36:02 +0000, alexanderdav wrote:  
[color=blue]

> It looks like it does not register the update somehow, when running  
> install or upgrade direct on the package…[/color]

I don’t have a SLES11 server here to test with, but you might check to  
see if there’s a ‘–force’ option, or download the RPM and use rpm -i –  
force to get it to reinstall the new version.

It seems that zypper thinks the updated version and the installed version  
are perhaps the same.

Jim

–  
Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10  
Novell Knowledge Partner

---

<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:** [December 6, 2011, 7:21am UTC](https://forums.suse.com/t/not-able-to-upgrade-self-built-packages/22022/5 "2011-12-06T07:21:47Z")

</div>

On Tue, 06 Dec 2011 04:25:00 GMT  
Jim Henderson [Jim.Henderson@SysOps.NSC](mailto:Jim.Henderson@SysOps.NSC) wrote:  
[color=blue]

> On Mon, 05 Dec 2011 15:36:02 +0000, alexanderdav wrote:  
> [color=green]
> 
> > It looks like it does not register the update somehow, when running  
> > install or upgrade direct on the package…[/color]
> 
> I don’t have a SLES11 server here to test with, but you might check  
> to see if there’s a ‘–force’ option, or download the RPM and use rpm  
> -i – force to get it to reinstall the new version.
> 
> It seems that zypper thinks the updated version and the installed  
> version are perhaps the same.
> 
> Jim
> 
> [/color]  
> Hi  
> Yes, --force or -f is an option 😉 You can also include the rpm  
> version (good for rolling back).

@OP, if it’s self built, are you updating the release or version number  
of the newer rpm, if not this will mean -f needs to be used.

–  
Cheers Malcolm Â°Â¿Â° (Linux Counter #276890)  
openSUSE 11.4 (x86\_64) Kernel 2.6.37.6-0.9-desktop  
up 5 days 5:25, 5 users, load average: 0.16, 0.09, 0.06  
GPU GeForce 8600 GTS Silent - Driver Version: 290.10

---

<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:** [December 20, 2011, 2:56pm UTC](https://forums.suse.com/t/not-able-to-upgrade-self-built-packages/22022/6 "2011-12-20T14:56:02Z")

</div>

Using rpm or force options is not a good idea. This should work without  
needing to apply any extra options. all this is also supposed to be  
automated, no interaction from then user when upgrading these  
packages..

I have changed both the release and version number. The package is  
listed as a upgrade when using zypper lu, but zypper up packagename does  
not work…

The only thing this package does is install a new file, but I see the  
same for other self built packages that are more advanced…

## – alexanderdav

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

---

<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:** [December 29, 2011, 4:36pm UTC](https://forums.suse.com/t/not-able-to-upgrade-self-built-packages/22022/7 "2011-12-29T16:36:02Z")

</div>

The reason for that is so called “vendor locks”, which is enabled by  
default. This means that zypper is safe by default and does not switch  
packages from one Vendor (Vendor:) tag to another Vendor Tag, unless  
forced.

It is actually imho a bug that “zypper lu” lists it as update, when the  
update can not actually be installed.

Once you’re on your “self-build” version, it will also not switch back  
to the Novell/SUSE provided version unless you force it to (for example  
via zypper patch or zypper install).

To switch to your version, do something like:

zypper in zypper-locks-1-4.noarch

which should produce output similar to

[color=blue]

> The following package is going to be upgraded:  
> zypper locks
> 
> The following package is going to change vendor:  
> zypper locks SUSE LINUX Products GmbH, Nuernberg, Germany →
> 
> 1 package to upgrade, 1 to change vendor.[/color]

## – 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=449109](http://forums.novell.com/showthread.php?t=449109)

---

<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 3, 2012, 3:56pm UTC](https://forums.suse.com/t/not-able-to-upgrade-self-built-packages/22022/8 "2012-01-03T15:56:02Z")

</div>

Hi,

This was not a vendor change problem. The problem is that the package  
version is 1-4, not for example 1.4.0. When changing the package version  
to 1.4 and supplying a update with version 1.4.1 zypper up package-name  
works.

I believe this is a bug in zypper, since zypper acknowledges that there  
is a available updates, but refuses to update the package.

I’ll submit a bug and see what Novell says.

## – alexanderdav

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