[opensuse-buildservice] Scheduler not pulling recommended packages
Hi, I am trying to find a way to cover unexpected dependencies indirectly pulled by a package, ie. emacs or vim pulling x11* (see https://progres s.opensuse.org/issues/16122) I had the idea of abusing OBS with a fake package that will install the package in the worker VM and check for pulled packages. But, it seems that because of the wanted build environment isolation, the scheduler is expected to pull only the necessary packages so the build can be performed offline (as in not network). The scheduler doesn't pull the recommended packages so zypper will not behave as in a real scenario inside the worker VM. Is that right? So, would it be possible to workaround it so that recommended packages are also taken into account? Kind Regards -- Sergio Lindo Mansilla <slindomansilla@suse.com> QA Engineer SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nürnberg Germany https://www.suse.com/ (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
On Mittwoch, 12. August 2020, 14:18:11 CEST wrote sergio:
Hi,
I am trying to find a way to cover unexpected dependencies indirectly pulled by a package, ie. emacs or vim pulling x11* (see https://progres s.opensuse.org/issues/16122)
I had the idea of abusing OBS with a fake package that will install the package in the worker VM and check for pulled packages. But, it seems that because of the wanted build environment isolation, the scheduler is expected to pull only the necessary packages so the build can be performed offline (as in not network). The scheduler doesn't pull the recommended packages so zypper will not behave as in a real scenario inside the worker VM. Is that right?
this is true for spec file based builds (rpm). For kiwi it is an option to include recommended (or even suggessted) packages.
So, would it be possible to workaround it so that recommended packages are also taken into account?
We could add an option to include also recommended packages... Is this about spec file builds? Or how do you execute zypper? -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
El mié, 12-08-2020 a las 14:21 +0200, Adrian Schröter escribió:
the scheduler is expected to pull only the necessary packages so the build can be performed offline (as in no network). The scheduler doesn't pull the recommended packages so zypper will not behave as in a real scenario inside the worker VM. Is that right?
this is true for spec file based builds (rpm).
For kiwi it is an option to include recommended (or even suggessted) packages.
I see, then I will look into using wiki. Thanks :) Do you have link with docs/getting-started/examples that could speed up my learning path for kiwi usage on OBS?
So, would it be possible to workaround it so that recommended packages are also taken into account?
We could add an option to include also recommended packages...
Is this about spec file builds?
Or how do you execute zypper?
At the moment my mindset is about using `_multibuild` to add the `qa- tess` like here: https://build.opensuse.org/package/view_file/home:SLindoMansilla:branch es:devel:tools:building/scons/scons.spec?expand=1 So, the idea was to execute a script on the %check section of the specfile to verify if unwanted dependencies were installed. But, I am open to better approaches. Kind Regards -- Sergio Lindo Mansilla <slindomansilla@suse.com> QA Engineer SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nürnberg Germany https://www.suse.com/ (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
participants (2)
-
Adrian Schröter -
sergio