Mailinglist Archive: opensuse-buildservice (46 mails)

< Previous Next >
Re: [opensuse-buildservice] Is "staticlinks" still working for images?
  • From: Adrian Schröter <adrian@xxxxxxx>
  • Date: Fri, 22 Feb 2019 09:27:27 +0100
  • Message-id: <1895428.NJJKuoOHc9@linux-ywca>
On Freitag, 22. Februar 2019, 09:25:04 CET Julio González Gil wrote:
On viernes, 22 de febrero de 2019 9:17:08 (CET) Adrian Schröter wrote:
On Freitag, 22. Februar 2019, 01:18:35 CET Julio González Gil wrote:
This could be the explanation:

the arm images are handled different due to the special layout on the ftp
server (actually it does not belong to github since it is custom scripts).

Then what's going on? Why "staticlinks" is not working anymore for our
SLE15/ openSUSE Leap 15 images?

As you can see, we have it at

And the Leap 42 images have the static link, but not the Leap 15:

Any idea?

please try the

Release: <CI_CNT>.<B_CNT>

config first as I mentioned below

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. Add
this to your project config:

Release: <CI_CNT>.<B_CNT>

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


Adrian Schroeter
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
email: adrian@xxxxxxx

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups