action #16122

[functional][u] Idea: a test / API that verifies that package X does not pull in (direct or indirect) package Y

Added by dimstar about 3 years ago. Updated 12 months ago.

Status:NewStart date:20/01/2017
Priority:LowDue date:
Assignee:-% Done:

0%

Category:New test
Target version:QA - future
Difficulty:
Duration:

Description

This is mainly interesting for textbased installs / minimal installs, where the installation of X is trying to be avoided..

We had two examples in the past:

  • emacs requires libgio which in turn depends on the existence of dbus-launch. dbus-launch was provided only by dbus-1-x11 and required X11 libs. As a result, installing emacs without X-libs was not possible
  • vim has just been reported to be linked to X-libraries (boo#1021043)

The idea is to get a framework / API, that can get a package to install and verify that a list of RPMs is not being pulled in by this.

openQA might be 'too late' - other ideas are welcome

History

#1 Updated by okurz about 3 years ago

  • Category set to New test
  • Target version set to future

#2 Updated by okurz almost 2 years ago

@dimstar: How about a OBS based multibuild package test as in https://build.opensuse.org/package/show/home:okurz/python-openqa_review with calls to rpm to check which packages are installed and which not?

#3 Updated by dimstar almost 2 years ago

okurz wrote:

@dimstar: How about a OBS based multibuild package test as in https://build.opensuse.org/package/show/home:okurz/python-openqa_review with calls to rpm to check which packages are installed and which not?

Might be an option - the main concern of course is if/how anybody will react on the failure and resolve it.

#4 Updated by okurz almost 2 years ago

Hm, I think this ticket would belong better in https://progress.opensuse.org/projects/opensuse-release-process but then not more people will see it I assume.

#5 Updated by okurz over 1 year ago

  • Subject changed from Idea: a test / API that verifies that package X does not pull in (direct or indirect) package Y to [functional][u] Idea: a test / API that verifies that package X does not pull in (direct or indirect) package Y

@dimstar Given the current description I am sorry that QSF will not be able to work on this ticket but we would be happy to try if you help us understand the requirements better. Could you try to specify more specific "acceptance criteria" for the ticket?

#6 Updated by okurz over 1 year ago

  • Target version changed from future to future

#7 Updated by simotek over 1 year ago

This would also be really useful for creating SLE-16 when the time comes to ensure that patterns are not pulling in packages they shouldn't the SLE releaes managers had to spend alot of time tracking down packages that were being pulled in by patterns when they shouldn't be, adding this api for tumbleweed will ensure we don't have any regressions here. If you look at line 4396 of https://build.opensuse.org/package/view_file/openSUSE:Leap:42.3/patterns-openSUSE/patterns-openSUSE.spec?expand=1 we used to have a minimal_base-conflicts pattern to prevent certain files being installed on a minimal system, this shouldn't be needed as of SLE/Leap 15 but it would be nice to have openQA tests to verify it.

#8 Updated by okurz 12 months ago

  • Priority changed from Normal to Low

let's focus more on improving our current tests and workflows first. Putting to "holding tank" :)

Also available in: Atom PDF