Project

General

Profile

Actions

action #90998

closed

[opensuse] prjconf_excluded_rpms: too strict about some package names

Added by dimstar about 3 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-GNOME-Live-x86_64-gnome-live@64bit fails in
prjconf_excluded_rpms

This new test assumes '*-upstream' to be invalid. In some cases, though, a package might be prepared for a branding package, with an -upstream split out, but no -openSUSE branding yet generated (as the need did not yet arise). This happened for example for GTK4 (as with gtk2/gtk3, the branding was split, but so far not need found to deviate from upstream, so no -branding-openSUSE has been generated).

Now, as soon as GTK4 is being installed, this test fails.

Also: the description of the test is misleading: there is no relation to 'prjconf' at all - the test has a hard-coded list of package names/patterns it does not expect to find on installed machines.

Test suite description

Maintainer: okurz@suse.de, dimstar@opensuse.org

Test for openSUSE GNOME Next Live-Media

EXCLUDE_MODULES is a workaround for https://bugzilla.opensuse.org/show_bug.cgi?id=1138401#c10 (except for opensuse_welcome, which is blacklisted on the GNOME live for space reasons)

Reproducible

Fails since (at least) Build 20210410 (current job)

Expected result

Last good: 20210408 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by tjyrinki_suse almost 3 years ago

  • Subject changed from prjconf_excluded_rpms: too strict about some package names to [opensuse] prjconf_excluded_rpms: too strict about some package names
  • Start date deleted (2021-04-12)
Actions #2

Updated by slo-gin over 1 year ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #3

Updated by dimstar over 1 year ago

  • Status changed from New to Closed

Technically we can consider this issue solved and the test being 'correct'.
The expectation is to provide openSUSE branding for everything that is branding prepared, even if the branding is not different initially.

Actions

Also available in: Atom PDF