Description of problem: I've ported python-pyp2rpm from fedora to mageia I'm using mageia for some HPC python related work, and so I'll be porting a whole bunch of python packages over
Created attachment 2811 [details] pyp2rpm mageia patch
Created attachment 2812 [details] template file for pyp2rpm (this is the spec file for the python package and not rpmbuild)
Created attachment 2813 [details] Spec file for rpmbuild
Created attachment 2814 [details] revised spec with one more patch
Attachment 2813 is obsolete: 0 => 1
Created attachment 2816 [details] change to metadata to make it a bit more robust
You might find it worthwhile to become a mageia packager Joseph. There is a great mentoring system to get people of all levels started and using the build system. There are mentors waiting for trainees now so it's a great time to join. More info here: https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
or ask directly in the dev ml like: https://www.mageia.org/pipermail/mageia-dev/2012-September/018705.html or https://www.mageia.org/pipermail/mageia-dev/2012-September/018707.html
imported (in mga4 at least)
Status: NEW => RESOLVEDResolution: (none) => FIXED