Reg- binclock porting from python 2 to python 3

[Rajeshkumar Pothiappan]

Hi Fedora Team,

  I would like to contribute in porting binclock from python 2 to python 3.
I found  http://fedora.portingdb.xyz/pkg/binclock/
https://admin.fedoraproject.org/pkgdb/package/rpms/binclock/

Please guide me where to start with or whom to contact and how to .

by
Rajeshkumar P

[Charalampos Stratakis]

Hello,

As it seems there is already an open bug regarding this package [0]

The patch that is posted there ports binclock to python 3 however the maintainer
hasn't responded as of yet. So the porting work has already been done basically, as a
downstream patch at least, only the changes need to be pushed by the maintainer. However
the best way, I think, would be to contact upstream about python 3 support.

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1305872

Regards,
Charalampos Stratakis


----- Original Message -----
From: "Rajeshkumarpothiappan" <gprkumar(a)gmail.com&gt;
To: python-devel(a)lists.fedoraproject.org
Sent: Sunday, May 29, 2016 9:24:38 AM
Subject: Reg- binclock porting from python 2 to python 3

Hi Fedora Team, 

I would like to contribute in porting binclock from python 2 to python 3. 
I found http://fedora.portingdb.xyz/pkg/binclock/ 
https://admin.fedoraproject.org/pkgdb/package/rpms/binclock/ 

Please guide me where to start with or whom to contact and how to . 

by 
Rajeshkumar P 


_______________________________________________
python-devel mailing list
python-devel(a)lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/[e-mail]...

[Tomas Orsava]

Hi Rajesh!

the `binclock` project is a bit problematic. As you can see in the note 
on the left side on the PortingDB, the upstream for this project is 
abandoned, emails bounce. If you go look into the Bugzilla link on the 
same page, you'll also find that someone has made a Python 3 patch, but 
the maintainer is not responding.

The best thing you could do is to fork the upstream (i.e. create a new 
repo on GH/BitBucket/GitLab and put the current source files there), and 
then use the patch on BZ to port it to Python 3. Test if it works, and 
then post to the Bugzilla that the software has a new upstream it should 
switch to.

Alternatively, you can try your luck on another package.
Are you interested more in porting Python code or Fedora spec files for 
Python projects?

Thank you for your initiative!
Tomas


[0] http://fedora.portingdb.xyz/pkg/binclock/


On 05/29/2016 09:24 AM, Rajeshkumarpothiappan wrote:
>  Hi Fedora Team,
>
>    I would like to contribute in porting binclock from python 2 to 
>  python 3.
>  I found http://fedora.portingdb.xyz/pkg/binclock/
>  https://admin.fedoraproject.org/pkgdb/package/rpms/binclock/
>
>  Please guide me where to start with or whom to contact and how to .
>
>  by
>  Rajeshkumar P
>
>
>
>  _______________________________________________
>  python-devel mailing list
>  python-devel(a)lists.fedoraproject.org
>  https://lists.fedoraproject.org/admin/lists/[e-mail]...

[Rajeshkumar Pothiappan]

Thanks  Charalampos,Thomas and others.
I am interested in porting Python code.
While choosing an Idle package, what are the other things I have to note ?
ie. you said some downstream, 
For your information,I am a noob in Fedora Development

[Rajeshkumar Pothiappan]

I am not aware of Python Spec file, and I  can work in Python projects too . 
I know core python well , I would like to contribute.
But I dont know where to start,what to do ,,
By random browsing , I found porting pacages  from Python 2 to Python 3.
It would be better if i were given a beginer level tasks in Python .
Thanks team.

[Charalampos Stratakis]

Hi again.

Personally I believe for starters the best way would be to package a python module which
has no binaries, or any other "weird" stuff in regards to it like Makefiles,
documentation building and so on.

The best way to distinguish that is to go to the SPEC file of the RPM that you are
interested in porting and check what is happening there. Of course you should go to the
packaging guidelines page and while it might be a lot of things to learn, a lot of aspects
and questions in regards to packaging can be found there. [0][1]

Also we have created an RPM porting guide for packagers interested in porting their
RPM's at least for simple packages [2].

Now I went through the list of packages and I found some things that might interest you.
For example:
http://fedora.portingdb.xyz/pkg/python-oslo-log/
http://fedora.portingdb.xyz/pkg/python-oslo-context/
http://fedora.portingdb.xyz/pkg/python-taskflow/
http://fedora.portingdb.xyz/pkg/python-pymod2pkg/
http://fedora.portingdb.xyz/pkg/python-fsmonitor/

Feel free to ping me on IRC or send me an email for further questions or recommendations.

[0] https://fedoraproject.org/wiki/Packaging:Guidelines
[1] https://fedoraproject.org/wiki/Packaging:Python
[2] http://python-rpm-porting.readthedocs.io/en/latest/index.html

Regards,
Charalampos Stratakis

[Rajeshkumar Pothiappan]

Thanks Charalampos Stratakis, 
I would like to package 
http://fedora.portingdb.xyz/pkg/python-fsmonitor/
yograterol is maintaining that package.
How to contact yograterol ?
Can i use yograterol(a)fedoraproject.org or any other way? 


Regards,
Rajeshkumar.P

[Petr Viktorin]

On 06/02/2016 10:25 AM, Rajeshkumar Pothiappan wrote:
>  Thanks Charalampos Stratakis, 
>  I would like to package 
>  http://fedora.portingdb.xyz/pkg/python-fsmonitor/
>  yograterol is maintaining that package.
>  How to contact yograterol ?
>  Can i use yograterol(a)fedoraproject.org or any other way?  
Hi Rajeshkumar,
Since the project has a Bugzilla bug open, it would be best to ask for
status and/or offer help there:
https://bugzilla.redhat.com/show_bug.cgi?id=1312340
You can check "Need additional information" from the maintainer.
The maintainer should get e-mails for all comments there. If he doesn't
respond in a week or so, you can either:
- write the patch anyway, and ask a provenpackager to review and push it
- (more officially) follow the Non-responsive Maintainer Policy [0] and
take over the package


[0]
https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers

-- 
Petr Viktorin