Mailinglist Archive: opensuse-bugs (4362 mails)

< Previous Next >
[Bug 704123] When updating packages, same version numbers in different repositories confuse YaST (and zypper?)

Ulrich Fieseler <ulfie_monster@xxxxxxxx> changed:

What |Removed |Added
InfoProvider|bin@xxxxxxxxxxxxxxx |

--- Comment #6 from Ulrich Fieseler <ulfie_monster@xxxxxxxx> 2012-03-15
13:29:16 UTC ---
Created an attachment (id=481608)
--> (
Part 1 of Solver testcase from YaST menu

Now that's a good deal of information you are collecting about my system...

Anyway, the bug currently affects libcurl4 (which I would like to have replaced
by version 7.23.1-64.1-x86_64 from
with priority 94 rather than
with priority 96, but the radio button changes to the latter on the versions
tab when I leave that package and return to it), libproj0 (which will be
updated to 4.8.0-19.1-x86_64 from
rather than where
the current version comes from, both with priority 98), and python-configobj
(which will be updated to 4.7.2-24.1-noarch from
with priority 98 rather than
with priority 96, again the latter being the source of the currently installed

Note that the vendor information for the libcurl4 version that always gets
automatically selected mentions the obs://... address of the repo actually
intended, but that does not match the repo name (unlike the other cases where
it matches the repo name)!

In addition, I am currently experiencing a strange behaviour regarding package
libenca0 which is installed from the base OSS repo with priority 99. YaST keeps
trying to replace it with version 1.13-19.1-x86_64 from with
priority 100, and that same version is also available from with
priority 96 (for which the vendor name openSUSE-Education is given, again not
matching the repo name).

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >