I have been around to write about it too, as it seemed to me as dev fork running wild with false positive. It happens :). Looking forward to postmortem. What worried me a bit and I hope is not a feature of the live process is an email from no-reply email address.
Jakub Čajka Jun 29, 2026, 15:43 by [email protected]: > I recently got some inactive packager notifications from what appears to be a > fork of the inactive packager repo on forge.f.o > > I initially replied as though it was legitimate, but I'm now wondering if > this isn't actually legit activity at all. > > It looks like the legitimate notifications and issues are in the > packaging/find-inactive-packagers repo, but these ones that I received came > from a fork with the following subject line: > > [jspaleta/find-inactive-packagers] Inactive packager detected for user > ctubbsii (Issue #335) > > (And another one from a duplicate issue #228, both issues having subsequently > been deleted or marked private apparently, since I can no longer see either) > > Clearly the notification itself is a false positive, since I've had activity > recently enough on bodhi, src, and devel@, that should have prevented me from > being marked inactive. > > Does anybody know what's going on here? I'm thinking maybe people should be > more careful about running this script from a fork? Or maybe the script > itself should automatically detect that it's a fork and operate in dry run > mode, without creating issues that tag people with false positives? But > perhaps I'm misunderstanding and these were supposed to be legitimate > notifications of inactivity? > > Regards, > Christopher > -- _______________________________________________ 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
