Miro Hrončok wrote: > Let's work together to make it less surprising for the dependent packages > owners when their dependencies are pulled from under them instead? > ... > dependent packages maintainers are likely kept in the dark here (unless they > maintain both the dependent and the dependency) and we should improve that.
On Miroslav's point about Packager Dashboard: The dashboard actually already tracks orphaned dependency trees and has an "Orphan Impacted" status with a 6-week countdown (and a dependency graph modal), but right now it's too passive. If you maintain dozens of packages, it's buried inside individual cards and easily missed. A few things I can improve on the dashboard to help with this: - Surface an upfront warning banner when any of your packages depend on a package currently on the 6-week orphan retirement clock. - Make the "FTBFS and orphans first" priority sort actually bubble these impacted packages to the top of the grid. - Add quick links inside the card to adopt the orphaned dependency (`fedpkg take`) or inspect its dist-git repo directly. The real gap, as Miro noted, is buildtime dependencies. Maintainers only discover the problem once the package fails in Koschei or mass rebuilds after the dependency is already gone. If we can get Oraculum to map Rawhide BuildRequires against the active orphan list, the dashboard could warn maintainers weeks before the failure ever hits Koji. -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
