Bug 613106 – Maintainership request: dev-python/python-sipsimple

• Product: Gentoo Linux
• Status: RESOLVED OBSOLETE

[Description Antoine Pinsard 2017-03-18 14:11:17 UTC]

As suggested by Pacho Ramos in bug #575772 (https://bugs.gentoo.org/show_bug.cgi?id=575772), I'd like to proxy maintain dev-python/python-sipsimple.

I've been waiting a few weeks before filing this maintainership request because I expected somebody actually using the package to be eventually willing to maintain it.

Yet, as nobody else seems interested in maintaining this package for now, I am willing to take care of it as much as I can. I'm not using it myself, but I have a tracker for upstream releases and I'm already maintaining it for Funtoo (which I won't need anymore if I proxy maintain it for Gentoo).

You can see the current ebuild I maintain here: https://github.com/apinsard/sapher-overlay/tree/master/dev-python/python-sipsimple It will of course require a few "gentooization" to be suitable for Gentoo.

[Comment 1 Göktürk Yüksek 2017-03-19 04:04:15 UTC]

Hi,

Feel free to file a Pull Request on github with the ebuilds you want to include in Gentoo. You should include the proxy-maint project in the metadata as similarly shown in this example[0]. In case you're not familiar with pull requests, we have a wiki page for it in [1]. At a quick glance at your ebuild, I'd like to point out that we need to fix the header so it exactly looks like [2]. We need proper KEYWORDS for non-live ebuilds (i.e. ~amd64 and ~x86 if you can test on it, let me know if you don't have the hardware for ~x86). The chmods will likely require '|| die'. If there's any bundling involved, we should unbundle as much as we can.

Thanks,

[0] https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers/User_Guide#How_proxy_maintainership_works
[1] https://wiki.gentoo.org/wiki/Gentoo_Github
[2] https://github.com/gentoo/gentoo/blob/master/header.txt

[Comment 2 Antoine Pinsard 2017-03-19 11:08:00 UTC]

Thank you Göktürk. Before submitting a pull request, I'd like to know what should be done about this issue: https://github.com/apinsard/sapher-overlay/issues/1 Considering that bug #612988 has to be sorted before adding >=dev-python/python-application-2.0.0 dependency. Should '>=dev-python/python-sipsimple-3.0.0' be masked until python-application 2.0.0 available in tree? Not publishing python-sipsimple 3.0.0 and 3.1.0 ebuilds at all?

This missing dependency, causes addressbook, streams, application, session and storage submodules to be unusable:

>>> from sipsimple import addressbook
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib64/python2.7/site-packages/sipsimple/addressbook.py", line 20, in <module>
    from application.python.weakref import defaultweakobjectmap
ImportError: cannot import name defaultweakobjectmap


Also, amd64 keyword is for 64bit x86 arch, and x86 keyword is for 32bit x86 arch, isn't it? I'm on a pure 64bit build (no multilib) on an AMD CPU, so I can't test x86 keyword.

[Comment 3 Antoine Pinsard 2017-07-17 16:38:24 UTC]

I am completely OK to leave this maintainership request to Mircea Sava.

[Comment 4 Michał Górny 2017-08-05 16:03:49 UTC]

We no longer use these bugs. See:

https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers/User_Guide#Taking_over_an_existing_package

Long story short:

1. If your request has been fulfilled already and you're the maintainer, ignore this.

2. If you have submitted the ebuilds separately, we'll handle it there. If that's via a bug, please make sure that proxy-maint@ is in CC. Feel free to ping us if things aren't moving forward for a long time.

3. If you haven't submitted anything yet, please submit a meaningful change to the package (bugfix, version bump, ebuild update...) along with the maintainer update and you'll become the maintainer when we merge it.

Sorry for the trouble.