On viernes, 17 de abril de 2020 15:46:39 (CEST) Pau Garcia Quiles wrote:
Hi
I am hitting a problem when trying to build Uyuni VMs with Kiwi because I cannot add an OBS URL as a repository in OBS (only projects or distributions are allowed).
This is how the docs (https://www.uyuni-project.org/pages/stable-version.html#serversetup) tell you to install Uyuni: 1. Install Leap 15.1 2. Add the "images" package repository: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable /images/repo/Uyuni-Server-POOL-x86_64-Media1/ 3. zypper ref & zypper in patterns-uyuni_server
When I want to build my VM images with Kiwi, I cannot add that URL in https://build.opensuse.org/projects/home:pagarcia:Uyuni:2020.04/meta
The workaround I have been using so far is adding two OBS projects: * Snapshot of Uyuni: systemsmanagement:Uyuni:Snapshots:2020.04 OBS project (fine, that's a snapshop and does not change) * systemsmanagement:Uyuni:Master:Other => This is a problem because this repository changes over time.
This is a problem because the VMs get rebuilt when new packages are available in systemsmanagement:Uyuni:Master:Other and therefore do not contain exactly the same as https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable /images/repo/Uyuni-Server-POOL-x86_64-Media1/
Is there a way to solve this?
Ideally, I should be able to add a URL as a repository (at least one that comes from OBS itself, so it should not require downloading anything). AFAIK this is not possible today.
Alternatively, I could also take snapshots of systemsmanagement:Uyuni:Master:Other for each release of Uyuni. This is currently possible but it will take some disk space.
FMPOV that's wasting disk space... and it's not the same as using the images. The images are used to filter packages (we don't have everything that's at systemsmanagement:Uyuni:Master:Other such as for example build dependencies). And the images can contain packages that for some reason are present at the OS codestream, but not published as part of the OS repositories (to be honest I think this happens with SLE but not with openSUSE, but I am not 100% sure). So IMHO the correct solution would be using the images somehow.
Thank you
Pau Garcia Quiles SUSE Manager Product Owner & Technical Project Manager SUSE Software Solutions Spain
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com