From Mageia wiki
Jump to: navigation, search


Migrate the package sources to Dist-Git, using Pagure as the frontend.


  • Name: Neal Gompa
  • Email:


This will require efforts by packagers to package distgit and pagure for Mageia and sysadmins to deploy it and migrate our current Dist-SVN to Dist-Git.

Current status

  • Targeted release: Mageia 8
  • Last updated: 2020/03/03
  • Percentage of completion: 0%

Detailed Description

We want to migrate our package sources from our SVN to Git, using a Fedora/OpenMandriva-style Dist-Git system, using Pagure as a frontend to enable modern PR-based workflow for packages.

Why it would be good for Mageia to do it

Moving to Dist-Git with Pagure as a frontend will make it easier for people to get involved in the development of Mageia. As PR-centric workflows have become the dominant development process (in large part due to the popularity of GitHub), offering people the ability to do "drive-by" contributions that can be reviewed and merged by packagers would increase the attractiveness to get actively involved in the development of the distribution as full contributors.

Test case

To be determined...


  • Package distgit
  • Package pagure
  • Convert svn+binrepo to distgit
  • Convert mgarepo to operate over Dist-Git (revive proyvind's branch which has code for this? rebase on latest repsys code?)
  • Deploy pagure as a frontend for distgit
    • It would also be a good idea to roll out a pagure frontend for our soft-git too...

Software / Packages Dependencies

  • distgit
  • pagure

What could disrupt development of this new feature

If the packaging and the repository conversion can't be done, then this can't be completed.


Early inclusion into Mageia 8 would allow for good appropriation of development and sysadmin resources to make this work.


If this fails to be ready for Mageia 8, then we continue with the current Dist-SVN setup.

Release Notes

Not applicable.


Associated Bugs

Packager comments