There are some packages in the openSUSE Build Service that "update"
packages from the default installation but that have a release number
minor than the package from the defaut installation. An example:
- openSUSE 10.3 comes with fileshareset-2.0-372 RPM, that has been
updated to fileshareset-2.0-372.5. The source RPM is
kdebase3-3.5.7-87[.5].
- KDE:KDE3 OBS repository, from where a lot of people updates to KDE
3.5.8, has fileshareset-2.0-41.1 from kdebase3-3.5.8-41.1 source RPM.

When I see such a thing should I report it to bugzilla?
This concrete case is problematic...
I use Smart and have KDE:KDE3 repository with a higher priority. So it
always prefers fileshareset-2.0-41.1 over fileshareset-2.0-372.5 even
if the release number is minor. I think that's the best I can do... I
don't know what fileshareset really is, but to avoid compatibility
problems is better to have all the packages from the same source RPM.
The problem happens if I try to use opensuse-updater. It tries to
install fileshareset-4865-0 patch to install fileshareset-2.0-372.5
package. Since fileshareset patch requires "kdebase3 == 3.5.7-87.5"
~# LANG=C zypper patch-info fileshareset
...
Provides:
patch: fileshareset == 4865-0

Requires:
atom: kdebase3-beagle == 3.5.7-87.5
atom: fileshareset == 2.0-372.5
atom: kdebase3-kdm == 3.5.7-87.5
atom: kdebase3-nsplugin == 3.5.7-87.5
atom: kdebase3-devel == 3.5.7-87.5
atom: kdebase3-session == 3.5.7-87.5
atom: kdebase3-32bit == 3.5.7-87.5
atom: kdebase3-ksysguardd == 3.5.7-87.5
atom: kdebase3-extra == 3.5.7-87.5
atom: kdebase3-samba == 3.5.7-87.5
atom: kdebase3-64bit == 3.5.7-87.5
atom: kdebase3 == 3.5.7-87.5 <<<<<<<<<<<<<--------------

but since I already have kde 3.5.8 zypper ends trying to install
kdebase3-32bit... and with it also 25 additional
packages/dependencies.


I have never trusted libzypp, so forget that part... but the OBS
fileshareset package with a relese number minor than the one from
default openSUSE 10.3 should be reported like a packaging bug?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to