releng/tickets

Fork 2

Orphaned package yields retirement warning although there was a migration (oxygen-icon-theme) #13412

New issue

Open

opened 2026-07-05 17:10:55 +00:00 by gsauthof · 2 comments

gsauthof commented

2026-07-05 17:10:55 +00:00

Describe the issue

On 2026-06-21 I received a 'Orphaned packages' report because the oxygen-icon-theme dependency of the quassel package was orphaned.

There are two issues with that report:

Firstly, for packages that depend on oxygen-icon-theme the listing seems to be wrong and misleading, because although the oxygen-icon-theme source package indeed was orphaned,
it was also migrated to the kf6-oxygen-icons source package which now does provide the oxygen-icon-theme package.

Thus, it looks like no change is needed in dependent packages such as quassel and thus the report shouldn't warn about this, as this creates confusion and wastes the time of affected maintainers.

Since the report warns:

Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.

I hope that the packages depending on oxygen-icon-theme aren't really auto-retired,
i.e. that the retirement process is more sophisticated and only retires the depending packages if their dependencies are truly broken.

Please clarify how this works.

Secondly, the report template needs to be adjusted for the new repository location, as it still reads:

The script creating this output is run and developed by Fedora
Release Engineering. Please report issues at its pagure instance:
https://pagure.io/releng/
The sources of this script can be found at:
https://pagure.io/releng/blob/main/f/scripts/find_unblocked_orphans.py

When do you need this? (YYYY/MM/DD)

2026-07-23, i.e. I need the clarification whether the auto-retirement of dependent package would affect packages that depend on oxygen-icon-theme.

When is this no longer needed or useful? (YYYY/MM/DD)

n/a

If we cannot complete this, what is the impact? [Dependencies/Blocker]

possibly dependent packages are retired that shouldn't be retired

Checklist

I have checked existing issues for duplicates
I have filled out all the fields above
I have provided relevant links or references (if applicable)

## Describe the issue  On 2026-06-21 I received a 'Orphaned packages' report because the oxygen-icon-theme dependency of the quassel package was orphaned. There are two issues with that report: Firstly, for packages that depend on oxygen-icon-theme the listing seems to be wrong and misleading, because although the oxygen-icon-theme **source** [package indeed was orphaned](https://src.fedoraproject.org/rpms/oxygen-icon-theme), it was also migrated to the kf6-oxygen-icons source package which now **does** [provide the oxygen-icon-theme package](https://src.fedoraproject.org/rpms/kf6-oxygen-icons/blob/rawhide/f/kf6-oxygen-icons.spec#_28). Thus, it looks like no change is needed in dependent packages such as quassel and thus the report shouldn't warn about this, as this creates confusion and wastes the time of affected maintainers. Since the report warns: > Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. I hope that the packages depending on oxygen-icon-theme aren't really auto-retired, i.e. that the retirement process is more sophisticated and only retires the depending packages if their dependencies are truly broken. Please clarify how this works. Secondly, the report template needs to be adjusted for the new repository location, as it still reads: > The script creating this output is run and developed by Fedora Release Engineering. Please report issues at its pagure instance: https://pagure.io/releng/ The sources of this script can be found at: https://pagure.io/releng/blob/main/f/scripts/find_unblocked_orphans.py ## When do you need this? (YYYY/MM/DD)  2026-07-23, i.e. I need the clarification whether the auto-retirement of dependent package would affect packages that depend on oxygen-icon-theme. ## When is this no longer needed or useful? (YYYY/MM/DD)  n/a ## If we cannot complete this, what is the impact? [Dependencies/Blocker]  possibly dependent packages are retired that shouldn't be retired --- ## Checklist - [x] I have checked existing issues for duplicates - [x] I have filled out all the fields above - [x] I have provided relevant links or references (if applicable)

patrikp added this to the Backlog project

2026-07-07 06:56:14 +00:00

patrikp added the

Backlog Status

Needs Review

label

2026-07-07 06:56:21 +00:00

jnsamyak commented

2026-07-10 06:04:59 +00:00

Owner

@gotmax, looping you in, since I believe you have looked at this script before?

gotmax23 commented

2026-07-11 21:51:28 +00:00

Member

Hi @gsauthof, I'm sorry for any confusion. There is nothing that you need to do here, since oxygen-icon-theme is still available but just provided by a different package. This false positive is a known problem with the dependency resolution in the orphaned packages report script¹, but the bug will not cause quassel or any other packages that depend on oxygen-icon-theme to be retired.

We should indeed change the "otherwise your package will be retired when the affected package gets retired" message in the report, as that is not actually how the process works. There are separate Fails To Build From Source and Fails to Install package policies that could kick in for any package with broken dependencies (whether caused by package retirements or other problems), but this is a separate process with separate tooling. The goal of the Orphaned Packages Process dependency report is just to provide a helpful report to notify maintainers so they can take advanced action if necessary. Only packages that are actually orphaned can get retired under the Orphaned Packages Report.

As for the issue with the old Pagure.io links, that should be fixed now.

This is the same root cause as #11460. There is a WIP PR from @jnsamyak in releng/tooling#13031 and an effort to rewrite the report script entirely in https://forge.fedoraproject.org/packaging/orphansv2. ↩︎

Hi @gsauthof, I'm sorry for any confusion. There is nothing that you need to do here, since `oxygen-icon-theme` is still available but just provided by a different package. This false positive is a known problem with the dependency resolution in the orphaned packages report script[^1], but the bug will **not** cause quassel or any other packages that depend on `oxygen-icon-theme` to be retired. We should indeed change the "otherwise your package will be retired when the affected package gets retired" message in the report, as that is not actually how the process works. There are separate [Fails To Build From Source and Fails to Install package policies](https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/) that could kick in for any package with broken dependencies (whether caused by package retirements or other problems), but this is a separate process with separate tooling. The goal of the Orphaned Packages Process dependency report is just to provide a helpful report to notify maintainers so they can take advanced action if necessary. Only packages that are actually orphaned can get retired under the Orphaned Packages Report. As for the issue with the old Pagure.io links, that should be fixed now. [^1]: This is the same root cause as https://forge.fedoraproject.org/releng/tickets/issues/11460. There is a WIP PR from @jnsamyak in https://forge.fedoraproject.org/releng/tooling/pulls/13031 and an effort to rewrite the report script entirely in https://forge.fedoraproject.org/packaging/orphansv2.

jnsamyak added

and removed

labels

2026-07-23 09:36:49 +00:00