Hello.
python-pytest-faulthandler has been retired in Fedora 33, it's blocked in Koji and therefore no longer tracked/scheduled by Koschei but it still appears on my dashboard as FTBFS package I should fix.
Would it make sense to ignore retired packages?
Metadata Update from @frantisekz: - Issue assigned to frantisekz
The package is not retired on Fedora 33:
$ koji list-pkgs --show-blocked --tag f33 --quiet --package python-pytest-faulthandler python-pytest-faulthandler f33 releng $ repoquery --repo=fedora-source --releasever 33 python-pytest-faulthandler python-pytest-faulthandler-0:1.6.0-6.fc33.src $ sudo dnf --releasever 33 install python3-pytest-faulthandler Last metadata expiration check: 2:57:41 ago on Wed Feb 17 07:37:25 2021. Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: python3-pytest-faulthandler noarch 1.6.0-6.fc33 fedora 15 k Transaction Summary ================================================================================ Install 1 Package Total download size: 15 k Installed size: 12 k Is this ok [y/N]: y Downloading Packages: python3-pytest-faulthandler-1.6.0-6.fc33.noarch 173 kB/s | 15 kB 00:00 -------------------------------------------------------------------------------- Total 60 kB/s | 15 kB 00:00 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : python3-pytest-faulthandler-1.6.0-6.fc33.noarch 1/1 Running scriptlet: python3-pytest-faulthandler-1.6.0-6.fc33.noarch 1/1 Verifying : python3-pytest-faulthandler-1.6.0-6.fc33.noarch 1/1 Installed: python3-pytest-faulthandler-1.6.0-6.fc33.noarch Complete!
That's strange because the package has been retired 8 months ago in rawhide branch which is 2 months before branching for Fedora 33.
Unfortunately, retiring packages is broken business :(
Okay, I'll ignore the warning on the dashboard. Feel free to close this issue.
Okay, glad it was not an issue in dashboard :)
Metadata Update from @frantisekz: - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.