zypper / vendor change


why does a

zypper in $REPO:$PACKAGE

not initiate a vendor change? Shouldn’t it work that way?

  | Alias                               | Name                                 | Enabled | Refresh | Priority | URI                        
5  | Virtualisation                      | Virtualisation                       | Yes     | Yes     |   80     | http://download.opensuse.org/repositories/Virtualization:/VirtualBox/openSUSE_11.2
11 | openSUSE:11.2:Update                | openSUSE:11.2:Update                 | Yes     | Yes     |   99     | http://download.opensuse.org/update/11.2/

S | Name                                     | Type       | Version                       | Arch   | Repository
v | virtualbox-ose                           | package    |               | i586   | Virtualisation
i | virtualbox-ose                           | package    | 3.0.6-9.11.2                  | i586   | Aktualisierungen für openSUSE 11.2-0
i | virtualbox-ose                           | package    | 3.0.6-9.11.2                  | i586   | openSUSE:11.2:Update
v | virtualbox-ose                           | package    | 3.0.6-9.10.4                  | i586   | openSUSE-11.2-Oss
  | virtualbox-ose                           | srcpackage |               | noarch | Virtualisation
  | virtualbox-ose                           | srcpackage | 3.0.6-9.11.2                  | noarch | Aktualisierungen für openSUSE 11.2-0
  | virtualbox-ose                           | srcpackage | 3.0.6-9.11.2                  | noarch | openSUSE:11.2:Update
i | virtualbox-ose                           | patch      | 1874                          | noarch | Aktualisierungen für openSUSE 11.2-0
i | virtualbox-ose                           | patch      | 1874                          | noarch | openSUSE:11.2:Update

zypper in Virtualisation:virtualbox-ose
Loading repository data...
Reading installed packages...
skipping package 'virtualbox-ose' (the newest version already installed)
Resolving package dependencies...

Nothing to do.

zypper if virtualbox-ose
Loading repository data...
Reading installed packages...

Information for package virtualbox-ose:

Repository: @System
Name: virtualbox-ose
Version: 3.0.6-9.11.2
Arch: i586
Vendor: openSUSE
Installed: Yes
Status: up-to-date
Installed Size: 23.0 MiB
Summary: VirtualBox OSE is an Emulator
VirtualBox OSE is an extremely feature rich, high performance product
for enterprise customers, it is also the only professional solution
that is freely available as Open Source Software under the terms of the
GNU Public License (GPL).

zypper in virtualbox-ose- does work.

I haven’t use the OSE version for quite a while, but I guess the one from the SUN repository is better, isn’t it?

That’s not the point here :wink:
I don’t use it myself :wink:

cat /etc/zypp/repos.d/Sun_VirtualBox.repo

name=Sun VirtualBox

rpm -qa | grep VirtualBox


By default, vendors changes are locked (for lot of quality reasons).

You can enforce vendors change by:

So why is there a possibility to do

zypper in $REPO:$PACKAGE

if it is not working as it should do?
What is it good for, then?

Dear IOz,

should we perhaps create an openFATE feature request on that?

IMHO it’s essential to allow simple vendor change through command line, at least when it comes to automated deployment.

Best Regards


will a:

zypper -C package=<version>

permanently change the vendor of the given package, too?

Best Regards

I’m about to add a request on openFate.

Thx for PM, got no notification on the answer here…

(sorry, my 1st openFate request. if something is to be changed…)

How can I find info about package available for update?

This does NOT work:
zypper if audacity

It provides info about existing package not the one available for update.

Real example:
zypper up
It’s output is:
Loading repository data…
Reading installed packages…

The following package updates will NOT be installed:
audacity clucene-core-devel gnuchess gstreamer-0_10-libnice

Nothing to do.

Simple query on installed packages gives following:
rpm -qa| grep audacity

Querying the same package by zypper proves it asking locally installed package not the one available for update… which is more important at the time as I should know what’s already installed so I don’t need to ask for that, right?
zypper if audacity
Information for package audacity:

Repository: @System
Name: audacity
Version: 1.3.12-12.1
Arch: x86_64
Vendor: openSUSE
Installed: Yes

However performing update indicate the available package has a different vendor
zypper up audacity
Loading repository data…
Reading installed packages…
There is an update candidate for ‘audacity’, but it is from different vendor. Use ‘zypper install audacity-1.3.13-1.pm.68.3.x86_64’ to install this candidate.
Resolving package dependencies…

So now, I’d like to see what vendor is that newer package from CLI. I don’t wanna to use GUI for that thought for me is only one possible way how to find out.

Any idea?
thx a lot,

Did you try “zypper info audacity-1.3.13-1.pm.68.3.x86_64” ?


Hey, welcome

Please note that you replied to a very old thread …

Yes, the thread has a very long beard. But it he is still available through search function and maybe someone finds this thread while searching for some answers.

The op said already that “zypper info” is not the solution.

The solution is the option “what-provides (wp)”:

zypper wp audacity
Loading repository data...
Reading installed packages...
S | Name     | Type    | Version     | Arch   | Repository       
  | audacity | package | 2.0.2-77.13 | x86_64 | packman          
  | audacity | package | 2.0.0-2.1.2 | x86_64 | openSUSE-12.2-Oss
  | audacity | package | 2.0.2-77.14 | i586   | packman          
  | audacity | package | 2.0.0-2.1.2 | i586   | openSUSE-12.2-Oss