Originally published at: Simplifying Package Submission Progress (15 August – 22 August) – GSoC ’25 – Fedora Community Blog
This week in the Fedora project, we did some small changes to the details and reporting of information in the service.
Small Changes
Better Review Comments
Previously, we were fetching the text version of the fedora-review report, the problem was it had way too much text for a comment and I had to parse the text file, to format the comment before posting into sections in collapsible tags manually.
While testing, I found out that the tool also publishes a json version with proper segregation of categories, items, checks and the related documentation to each rule. It made it much easier to parse and comment.
Clearer Status Reporting
Another small change was to report the status for install-ability and rpmlint checks separately from Testing Farm. My mentor suggested this approach to make it easier for users to interpret feedback.
One can check detailed logs of each run by going to dashboard through the details button.
Testing
I’m still working through some challenges with unit testing. The tricky part is mocking external dependencies to properly test the integration code in the service. The aim is to catch smaller bugs earlier with better coverage in ogr, the library that’s being used for interacting with forgejo.
What’s Next?
We almost have a way to review packages directly within a Forgejo repository. This will allow us to set up a dedicated repo for performing package reviews with automated feedback from tools and experienced packagers.
In the future, this idea could be extended further as Fedora moves to Forgejo, even handling dist-git setup.
For now, my next tasks are:
- Deploying the service
- Writing setup instructions for local development
- Setting up the bot account
- Completing the work needed for merging the relevant code upstream
I’m grateful to my mentor, František Lachman, for his constant support and guidance.