news
Fedora Community Blog: Simplifying Package Submission, Progress
-
Fedora Project ☛ Fedora Community Blog: Simplifying Package Submission Progress (15 July – 22 July) – GSoC ’25
Hi, I am Mayank Singh, welcome back to this blog series on the progress of the new package submission prototype, if you aren’t familiar with the project, feel free to check out the previous blogpost here.
Extending Forgejo support
As Forgejo is expected to become the git forge for Fedora in future and based on community discussions. I thought it did be great to support Forgejo in this project.
-
Fedora Project ☛ Fedora Community Blog: Simplifying Package Submission, Progress (22 July – 29 July) – GSoC ’25
This week in the project involved bug fixes, integration cleanup and small improvements.
Bug Fixes and Workarounds
A key function required for the Forgejo integration which is used to fetch files from repositories was broken in the current Fedora 42 release due to an upstream bug in Forgejo’s OpenAPI spec. While the bug is already fixed in newer versions, it couldn’t be backported cleanly due to dependency constraints.
To move forward, I upgraded the service to run on Fedora Rawhide. However, Rawhide had its own quirks, the
celery
package was broken. To work around this, I installedcelery
directly from PyPI instead, which resolved the issue for now.There were also several issues related to how data was being passed between the celery tasks. In particular, raw comment objects from Forgejo events were being passed around, which are not JSON-serializable and caused failures. With help from my mentor, added fixes in the logic to ignore the problematic object from being included in the payload.
Improvements and features