Description of problem: During a recent discussion with a user trying to get an alternative i3 based Fedora spin going we encountered something unthinkable - the org_fedora_realm Anaconda addon! That must have been some fluke we thought, that think certainly no longer exists since relamd support was moved from the addon to Anaconda in the 2013-2014 timeframe (to provided better support for configuration from kickstart). But turns out we were wrong! :D The anaconda-realmd package is actually still there, although not required by any other package nor listed in any of the comps group, it has been there since 2013 and without any human interaction survived 14 Fedora mass rebuilds (!) without any issue. Preaty much the only way to find out something is not right is to run "dnf install anaconda*" - which the user trying to get an i3 spin going did & enocuntered weird tracebacks coming from the long though dead Anaconda realmd addon. The code being ~7 years old has of course never been ported from Python 2, so it now throws a traceback when executed on the Python 3 interpreter. If it still somehow worked on Python 3 the package might still have been missed. In any case it Version-Release number of selected component (if applicable): anaconda-realmd-0.2-14.fc34 How reproducible: Always once Python 3 became default. Steps to Reproduce: 1. run "dnf install anaconda*" 2. check anaconda-realmd gets installed (among other things) 3. run the "liveinst" script Actual results: Tracebacks due to code (such as exception rising) not being Python 3 compatible show up & prevent Anaconda from starting up. Expected results: The anaconda-realmd package is not installed as it is no longer in the Fedora repositories.
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.
Hello Stef, the steps to retire a package are outlined here: https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/ Alternatively, you could orphan the package https://docs.fedoraproject.org/en-US/package-maintainers/Package_Orphaning_Process/ so that we can then pick it up and go through the process ourselves. The dist-git repo is here https://src.fedoraproject.org/rpms/anaconda-realmd .
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.