This could be the explanation: https://github.com/openSUSE/open-build-service/issues/6997

On lunes, 11 de febrero de 2019 12:35:35 (CET) Julio González Gil wrote: > Any idea? Anyone? :-) > > On viernes, 25 de enero de 2019 11:39:38 (CET) Julio González Gil wrote: > > We upgraded one of our products to use the new version of product > > definitions, and it seems "staticlinks" does not work anymore, as the > > 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 build > > numbers at the same time, as I think it was the case with "staticlinks"?

On viernes, 22 de febrero de 2019 9:17:08 (CET) Adrian Schröter wrote: 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 https://build.opensuse.org/project/prjconf/ systemsmanagement:sumaform:images:libvirt And the Leap 42 images have the static link, but not the Leap 15: https://download.opensuse.org/repositories/systemsmanagement:/sumaform:/ images:/libvirt/images/ Any idea?

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

wrote: > > > > We upgraded one of our products to use the new version of product > > > > definitions, and it seems "staticlinks" does not work anymore, as > > > > the > > > > 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 > > > > build > > > > numbers at the same time, as I think it was the case with > > > > "staticlinks"? > > 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)

On viernes, 22 de febrero de 2019 9:27:27 (CET) Adrian Schröter wrote: Sorry, didn't notice that part of your message on the previous email. I tried now, it works for https://build.opensuse.org/project/prjconf/ systemsmanagement:sumaform:images:libvirt (https://download.opensuse.org/ repositories/systemsmanagement:/sumaform:/images:/libvirt/images/) But for some reason not for Uyuni: https://build.opensuse.org/project/prjconf/ systemsmanagement:Uyuni:Master (https://download.opensuse.org/repositories/ systemsmanagement:/Uyuni:/Master/images-openSUSE_Leap_15.0/iso/ and https:// download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Master/images- openSUSE_Leap_15.0/repo/) And same for SUSE Manager at the IBS. I suspect this has something to do with the product definition, as the images at https://download.opensuse.org/repositories/systemsmanagement:/sumaform:/ images:/libvirt/images/ are now in format: opensuse423.x86_64-0.1.0-Build19.1.qcow2 While the images (repos and ISOs) are informat: Uyuni-Proxy-4.0-DVD-x86_64-Build16.1-Media1.iso Could it be something else we need to adjust at prjconfig or at the product_converter service (https://build.opensuse.org/package/view_file/ systemsmanagement:Uyuni:Master/000product/_service?expand=1)? BTW: Should I fill a bug somehwere? > > > > On lunes, 11 de febrero de 2019 12:35:35 (CET) Julio González Gil > > wrote: > > > > > Any idea? Anyone? :-) > > > > > > > > > > On viernes, 25 de enero de 2019 11:39:38 (CET) Julio González Gil > > > > wrote: > > > > > > We upgraded one of our products to use the new version of > > > > > > product > > > > > > definitions, and it seems "staticlinks" does not work anymore, > > > > > > as > > > > > > the > > > > > > 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 > > > > > > build > > > > > > numbers at the same time, as I think it was the case with > > > > > > "staticlinks"? > > > > > > 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)