Mailinglist Archive: opensuse-buildservice (144 mails)

< Previous Next >
Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not?
On Sun, 08 Sep 2019, 14:12:45 +0200, Andreas Schwab wrote:
On Sep 08 2019, Manfred Hollstein <mhollstein@xxxxxxxxxxx> wrote:

Building firefox68 succeeds, although I don't understand why it doesn't
pick up rust-cbindgen-0.9.0 which perfectly fulfills the BuildRequire,

There is no rust-cbindgen-0.9.0.rpm, there is only rust-cbindgen.rpm,
which has been picked up from home:manfred-h:TEST/rust-cbindgen-0.8.7,
with version 0.8.7.

then, why do both versions exist at



But, firefox69 fails with "unresolvable": nothing provides rust-cbindgen >=

Because rust-cbindgen.rpm has version 0.8.7.


zypper ar
zypper ref
zypper se -s rust-cbindgen
Loading repository data...
Reading installed packages...

S | Name | Type | Version | Arch | Repository
| rust-cbindgen | package | 0.9.0-lp151.3.1 | x86_64 | TEST
| rust-cbindgen | package | 0.8.7-lp151.8.1 | x86_64 | TEST
| rust-cbindgen | srcpackage | 0.9.0-lp151.3.1 | noarch | TEST
| rust-cbindgen | srcpackage | 0.8.7-lp151.8.1 | noarch | TEST

so it's there and would be installed in version 0.9.0-lp151.3.1 when running

zypper in rust-cbindgen

Am I wrong assuming this ought to work?

Yes. A repository can only hold a single version of a binary package
with a given name. If you want to provide different versions of a
package, you need to build them in different repositories, and control
the visibilty via the repository path. Alternatively, you can rename
the binary package to make its name unique.

See above. AFAICS, the update repos work exactly like this - they just
add a newer version on top of the stack, but in the same repo.



< Previous Next >
Follow Ups