#250 Incorrect upstream source for rtslib package

v1.0_(example)
open
nobody
rtslib (1)
5
2013-04-03
2013-04-01
No

Hi PyPI admins,

I'm filing a request as the Linux kernel SCSI target subsystem maintainer to address an issue with the incorrect ownership + upstream source of the rtslib package here:

https://pypi.python.org/pypi/rtslib/

The problem is that the owner (agrover) of a downstream Fedora fork of rtslib (rtslib-fb) has illegitimately stated upstream ownership of rtslib in pypi, that is now starting to cause confusion with downstream distros due to the fact rtslib and rtslib-fb are not python object class compatible.

To avoid further confusion and end-user impact, please allow the original author of rtslib, Jerome Martin (tramjoe.merin@gmail.com) or myself (nab@linux-iscsi.org) control of rtslib on pypi as soon as possible, and either remove the offending rtslib 2.1.fbXX source or move it to a rtslib-fb name designation to prevent further downstream confusion.

Thank you,

--nab

Related

Support Requests: #250

Discussion

  • Richard Jones
    Richard Jones
    2013-04-03

    Please contact the current owner of the package name and try to resolve this with him. He has the power to grant additional package ownership permissions.

    Changes of ownership performed by PyPI admins are an absolute last resort.

     
  • On Wed, 2013-04-03 at 02:34 +0000, Richard Jones wrote:

    Please contact the current owner of the package name and try to
    resolve this with him.

    Unfortunately, he did not bother to ask us (as the offical upstream) the
    first time around. ;(

    He has the power to grant additional package ownership permissions.

    We are not looking for co-ownership permissions. He needs to move his
    downstream fork to a 'rtslib-fb' name designation to avoid further
    confusion with non Fedora based distros.

    As mentioned, given that his fork is not object class compatible with
    upstream rtlsib code, this is starting to cause problems downstream for
    existing users.

    Changes of ownership performed by PyPI admins are an absolute last
    resort.

    Yes, hence the support request. I'll ask him off-list nicely, but given
    the history involved I'm not optimistic at all.

    --nab


    [support-requests:#250] Incorrect upstream source for rtslib package

    Status: open
    Labels: rtslib
    Created: Mon Apr 01, 2013 01:44 AM UTC by Nicholas A. Bellinger
    Last Updated: Mon Apr 01, 2013 01:44 AM UTC
    Owner: nobody

    Hi PyPI admins,

    I'm filing a request as the Linux kernel SCSI target subsystem
    maintainer to address an issue with the incorrect ownership + upstream
    source of the rtslib package here:

    https://pypi.python.org/pypi/rtslib/

    The problem is that the owner (agrover) of a downstream Fedora fork of
    rtslib (rtslib-fb) has illegitimately stated upstream ownership of
    rtslib in pypi, that is now starting to cause confusion with
    downstream distros due to the fact rtslib and rtslib-fb are not python
    object class compatible.

    To avoid further confusion and end-user impact, please allow the
    original author of rtslib, Jerome Martin (tramjoe.merin@gmail.com) or
    myself (nab@linux-iscsi.org) control of rtslib on pypi as soon as
    possible, and either remove the offending rtslib 2.1.fbXX source or
    move it to a rtslib-fb name designation to prevent further downstream
    confusion.

    Thank you,

    --nab


    Sent from sourceforge.net because you indicated interest in
    https://sourceforge.net/p/pypi/support-requests/250/

    To unsubscribe from further messages, please visit
    https://sourceforge.net/auth/subscriptions/

     

    Related

    Support Requests: #250