Created attachment 9928 [details]
modified spec to miniupnpc

Take the build for python modules from fedora's spec

SRPM for nicotine+ http://ftp.blogdrake.net/RPMS/SRPMS/nicotine%2b-1.4.1-1bdk.mga6.src.rpm , based in fedora

(In reply to katnatek from comment #1)
> Created attachment 9928 [details]
> modified spec to miniupnpc
> 
> Take the build for python modules from fedora's spec

@ katnatek

Note that there is an existing package request for nicotine+, bug #4628

Also, note that new package requests need to be done for Cauldron first. After that, a request can be made to backport it to Stable.

Maybe this report can be changed into a request to adjust miniupnpc for nicotine+

Assigning to the python maintainers.

Component: New RPM package request => RPM Packages
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=4628
CC: (none) => marja11
Summary: nicotine+ A graphical client for the SoulSeek peer-to-peer system => Please adjust miniupnpc for nicotine+ (A graphical client for the SoulSeek peer-to-peer system)
Source RPM: (none) => miniupnpc

(In reply to Marja van Waes from comment #3)
> @ katnatek
> 
> Note that there is an existing package request for nicotine+, bug #4628
> 
> Also, note that new package requests need to be done for Cauldron first.
> After that, a request can be made to backport it to Stable.
> 
> Maybe this report can be changed into a request to adjust miniupnpc for
> nicotine+
> 
> Assigning to the python maintainers.

I understand that nicotine+ have to pass to all the cycle but for miniupnpc is just a little update to an already existing package.

Thanks for the information

(In reply to katnatek from comment #4)
> (In reply to Marja van Waes from comment #3)

> > Assigning to the python maintainers.
> 
> I understand that nicotine+ have to pass to all the cycle but for miniupnpc
> is just a little update to an already existing package.
> 


Really assigning to the python maintainers, now :-/

(In reply to katnatek from comment #1)
> Created attachment 9928 [details]
> modified spec to miniupnpc
> 
> Take the build for python modules from fedora's spec

Thanks :-)

In case you have some time and are interested in making things things easier for our packagers, then you'll want to read the sections 
 
 1 Apprentice Work-flow
     1.1 Preparations
     1.2 Updating a packagehttps://wiki.mageia.org/en/Packagers_Howto_start

to learn how to make an "svn diff" patch of the spec file. Such patches make it much easier to see what changes were made and can be attached to bug reports.

Assignee: bugsquad => python

Sorry for the messed-up link. It should be:

 https://wiki.mageia.org/en/Packagers_Howto_start

By the way, can some one tell why when i rebuild miniupc in my system, the patch step ask me by the filename?
I give CMakeLists.txt, but is not the normal behaviour for patches.
I think maybe i miss some package in my try to keep disk space but no idea of what could be.

(In reply to katnatek from comment #7)
> By the way, can some one tell why when i rebuild miniupc in my system, the
> patch step ask me by the filename?
> I give CMakeLists.txt, but is not the normal behaviour for patches.
> I think maybe i miss some package in my try to keep disk space but no idea
> of what could be.

My mistake i don't know why change the patch line from p1 to p0.
I have to make some adjust to get the build end successful in a clean installed Mageia 6 and in the fedora's copr.

https://forums.mageia.org/en/viewtopic.php?f=10&t=12265

I will upload the new spec

Created attachment 9977 [details]
Revised version of spec for miniupnpc

Created attachment 11096 [details]
Updated spec to generate python modules

Hi this new spec works for the current version of miniupnpc in cauldron

Attachment 9977 is obsolete: 0 => 1
Attachment 9928 is obsolete: 0 => 1

Closing due bug#4628 is FIXED

Resolution: (none) => FIXED
Status: NEW => RESOLVED