Mailinglist Archive: opensuse-buildservice (46 mails)

< Previous Next >
Re: [opensuse-buildservice] Is "staticlinks" still working for images?
On viernes, 22 de febrero de 2019 9:27:27 (CET) Adrian Schröter wrote:
please try the

Release: <CI_CNT>.<B_CNT>

config first as I mentioned below

Sorry, didn't notice that part of your message on the previous email.

I tried now, it works for
systemsmanagement:sumaform:images:libvirt (

But for some reason not for Uyuni:
systemsmanagement:Uyuni:Master (
systemsmanagement:/Uyuni:/Master/images-openSUSE_Leap_15.0/iso/ and https://

And same for SUSE Manager at the IBS.

I suspect this has something to do with the product definition, as the images
images:/libvirt/images/ are now in format:


While the images (repos and ISOs) are informat:


Could it be something else we need to adjust at prjconfig or at the
product_converter service (

BTW: Should I fill a bug somehwere?

On lunes, 11 de febrero de 2019 12:35:35 (CET) Julio González Gil

Any idea? Anyone? :-)

On viernes, 25 de enero de 2019 11:39:38 (CET) Julio González Gil

We upgraded one of our products to use the new version of product
definitions, and it seems "staticlinks" does not work anymore, as
repositories are generated with buildnumbers.

So far I discovered that using:

Repotype: slepool:nobuildid

OBS able to generate repositories without build numbers.

However: is it possible to have both repositories with and without
numbers at the same time, as I think it was the case with

In your case, the solution of skipping the release number should help.
this to your project config:

Release: <CI_CNT>.<B_CNT>

(the lp150 prefix should have been configured only for rpm builds in
15.0 config)

Julio González Gil <jgonzalez@xxxxxxxx>
Release Engineer
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg
Tel: +49-911-74053-0; Fax: +49-911-7417755;
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard,
Graham Norton, HRB 21284 (AG Nürnberg)
< Previous Next >
Follow Ups