action #28815

compile a list of packages that are from sle but not maintained there

Added by lnussel over 2 years ago. Updated over 1 year ago.

Status:ClosedStart date:07/03/2018
Priority:NormalDue date:25/04/2018
Assignee:AndreasStieger% Done:

100%

Category:Release Engineering
Target version:Polished
Duration: 36

Description

some packages are marked as coming from SLE even though not all or none of it's source packages are actually maintained there. Need to compute a list and discuss with maintenance.


Related issues

Copied to openSUSE Leap 15.1 - action #47819: compile a list of packages that are from sle but not main... Closed 20/02/2019 10/04/2019

History

#1 Updated by lnussel about 2 years ago

  • Due date changed from 09/02/2018 to 25/03/2018
  • Start date changed from 22/01/2018 to 07/03/2018

#2 Updated by lnussel about 2 years ago

  • Assignee set to jberry

Jimmy, could you help me with this please?

Basically we need a script that looks at all binary packages in Leap that come from SLE based source packages. List all source and binary packages that are not in any kiwi file in 000prodoct on SLE side (ie unwanted or unsorted).

#3 Updated by jberry about 2 years ago

Rather than just source packages which may be in SLE and maintained there, but contain subpackages (binaries) that are not shipped need to look at binaries. Roughly translated:

for binary in binaries:
  if binary.origin = SLE and binary in unwanted:
    some_new_list.append(binary.name)

Where is the list to be placed?

Unsorted would appear to be a full package list? Ignore anything in 000product/unneeded.yml or 000package-groups/groups.yml#UNWANTED?

#4 Updated by lnussel about 2 years ago

Sorry, I missed the question :-(

jberry wrote:

Rather than just source packages which may be in SLE and maintained there, but contain subpackages (binaries) that are not shipped need to look at binaries. Roughly translated:


for binary in binaries:
if binary.origin = SLE and binary in unwanted:
some_new_list.append(binary.name)

Where is the list to be placed?

Dashboard or even just the output of a script that we can give to maintenance.

Unsorted would appear to be a full package list? Ignore anything in 000product/unneeded.yml or 000package-groups/groups.yml#UNWANTED?

I think that is the input, yes. Looking at the output works too though as none of the generated kiwi files would contain the binaries.

#5 Updated by lnussel about 2 years ago

  • Due date changed from 25/03/2018 to 13/04/2018

#6 Updated by jberry almost 2 years ago

  • Status changed from New to Feedback

#7 Updated by jberry almost 2 years ago

full list

Also, 1489 should allow for easy usage by maintenance via:

zypper in openSUSE-release-tools
osrt-unmaintained openSUSE:Leap:15.0

#8 Updated by jberry almost 2 years ago

Verified the above works by installing in container.

#9 Updated by jberry almost 2 years ago

You noted that debuginfo binaries should be removed. There are also -debug- named packages and -debugsource. Is there a list of everything that should be excluded and/or who should I contact to review from maintenance?

#10 Updated by lnussel almost 2 years ago

I think we have filters for *-debuginfo and *-debugsource in other tools also

The contact would be Andreas Stieger

#11 Updated by lnussel almost 2 years ago

  • Due date changed from 13/04/2018 to 25/04/2018

#13 Updated by jberry almost 2 years ago

  • Assignee changed from jberry to AndreasStieger
  • % Done changed from 0 to 100

Merged. Per lnussel comment, Andreas could you have a look?

# from openSUSE:Tools repo
zypper in openSUSE-release-tools
osrt-unmaintained openSUSE:Leap:15.0

updated full list

#14 Updated by jberry almost 2 years ago

discovered and resolved issue which effects this tool in pr#1505

updated list

#15 Updated by jberry almost 2 years ago

Disregard above link as I ran without rebasing on latest master so it includes debug packages.

updated list

#16 Updated by AndreasStieger almost 2 years ago

From Leap 42.3 maintenance experience, we can disregard discrepancies in subpackages being included or excluded. As long as the source container is maintained in SLE in some way or another then we will do maintenance updates for it, and thus inherit the code fixes for Leap.

#17 Updated by lnussel almost 2 years ago

So are you fine with the provided information Andreas, ie can the task be closed?

#18 Updated by lnussel almost 2 years ago

  • Status changed from Feedback to Closed

so information was handed over, closing as done

#19 Updated by lnussel over 1 year ago

I think sle-module-development-tools-obs-ftp-POOL-*.kiwi spoiled the list. The module actually does not map to channel so I think the content there is also unmaintained.

#20 Updated by lnussel about 1 year ago

  • Copied to action #47819: compile a list of packages that are from sle but not maintained there added

Also available in: Atom PDF