Comment # 9 on bug 900092 from Michael Andres

> job: install libvlc5	-3.0.0-2014100306.4.x86_64
> job: install vlc	-2.1.5-114.3.x86_64
> job: install vlc-noX	-2.1.5-114.3.x86_64
> job: install vlc-qt	-2.1.5-114.3.x86_64

PK simply selects the highest available version for individual packages. This
makes it fail in your scenario.

'zypper up' issues only one job: 'update all packages'. This leaves it to the
resolver to select the matching packages and the resolver sees the conflict,
thus is able to avoid it.

----
After a glimpse at the zypp-backend code I see the backend_get_updates_thread
calling zypp_get_updates which calls zypp_get_package_updates which finally
calls getZYpp()->resolver()->doUpdate(). This call issues a 'update all
packages' job, which is also visible in the logs. PK even sees the correct
libvlc5;2.1.5-114.3;x86_64;VideoLAN as result of this call:

> 2014-10-14 18:06:53 <1> linux.site(22582) [packagekit] pk-backend-zypp.cpp(zypp_get_package_by_id):880 libvlc5;2.1.5-114.3;x86_64;VideoLAN
> 2014-10-14 18:06:53 <1> linux.site(22582) [packagekit] pk-backend-zypp.cpp(zypp_get_package_by_id):933 found (18958)libvlc5-2.1.5-114.3.x86_64(VideoLAN)
> 2014-10-14 18:06:53 <1> linux.site(22582) [packagekit] pk-backend-zypp.cpp(backend_update_packages_thread):3131 sel package libvlc5

But it looks like only the name 'libvlc5' survives and finally leads to
selection of the highest available 'libvlc5'

> 2014-10-14 18:06:53 <1> linux.site(22582) [libsolv] PoolImpl.cc(logSat):111 job: install libvlc5-3.0.0-2014100306.4.x86_64


I need to have a closer look at the code.... Maybe Coolo knows why?