Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #13786 > unrolled thread

Please enable me transfering python-bioblend to Debian Med team

Back to article view | Back to linux.debian.maint.python

Contents

  Please enable me transfering python-bioblend to Debian Med team Andreas Tille <andreas@an3as.eu> - 2021-12-19 17:10 +0100
    Re: Please enable me transfering python-bioblend to Debian Med team Andreas Tille <andreas@an3as.eu> - 2021-12-21 15:50 +0100
      Re: Please enable me transfering python-bioblend to Debian Med team Pierre-Elliott Bécue <peb@debian.org> - 2021-12-22 18:30 +0100
        Re: Please enable me transfering python-bioblend to Debian Med team Andreas Tille <tille@debian.org> - 2021-12-22 19:50 +0100
          Re: Please enable me transfering python-bioblend to Debian Med team Pierre-Elliott Bécue <peb@debian.org> - 2021-12-22 20:20 +0100
            Re: Please enable me transfering python-bioblend to Debian Med team Nilesh Patra <nilesh@debian.org> - 2021-12-22 20:50 +0100
              Re: Please enable me transfering python-bioblend to Debian Med team Pierre-Elliott Bécue <peb@debian.org> - 2021-12-22 21:50 +0100
                Re: Please enable me transfering python-bioblend to Debian Med team Andreas Tille <andreas@an3as.eu> - 2022-01-11 15:40 +0100
                  Re: Please enable me transfering python-bioblend to Debian Med team Nilesh Patra <nilesh@nileshpatra.info> - 2022-01-15 16:00 +0100
                    Re: Please enable me transfering python-bioblend to Debian Med team Stefano Rivera <stefanor@debian.org> - 2022-01-15 20:30 +0100
                      Re: Please enable me transfering python-bioblend to Debian Med team Andreas Tille <andreas@an3as.eu> - 2022-01-15 20:50 +0100
          Re: Please enable me transfering python-bioblend to Debian Med team Sandro Tosi <morph@debian.org> - 2021-12-22 21:20 +0100
            Re: Please enable me transfering python-bioblend to Debian Med team Andreas Tille <tille@debian.org> - 2021-12-22 22:10 +0100
              Transfering packages from Debian Med to DPT (Was: Please enable me  transfering python-bioblend to Debian Med team) Andreas Tille <tille@debian.org> - 2021-12-23 09:30 +0100
                Re: Transfering packages from Debian Med to DPT (Was: Please enable  me transfering python-bioblend to Debian Med team) Nilesh Patra <nilesh@onenetbeyond.org> - 2021-12-23 10:00 +0100
                  Re: Transfering packages from Debian Med to DPT (Was: Please enable  me transfering python-bioblend to Debian Med team) Andreas Tille <tille@debian.org> - 2021-12-23 11:10 +0100
                    Re: Transfering packages from Debian Med to DPT (Was: Please enable  me transfering python-bioblend to Debian Med team) Sandro Tosi <morph@debian.org> - 2021-12-23 16:00 +0100
                      Re: Transfering packages from Debian Med to DPT (Was: Please enable  me transfering python-bioblend to Debian Med team) Andreas Tille <tille@debian.org> - 2021-12-23 17:30 +0100
                        Re: Transfering packages from Debian Med to DPT (Was: Please enable  me transfering python-bioblend to Debian Med team) Sandro Tosi <morph@debian.org> - 2022-01-02 03:30 +0100
                          Re: Transfering packages from Debian Med to DPT (Was: Please enable  me transfering python-bioblend to Debian Med team) Nilesh Patra <nilesh@onenetbeyond.org> - 2022-01-02 08:40 +0100
                            Re: Transfering packages from Debian Med to DPT (Was: Please enable  me transfering python-bioblend to Debian Med team) Andreas Tille <tille@debian.org> - 2022-01-02 10:20 +0100
                          Re: Transfering packages from Debian Med to DPT (Was: Please enable  me transfering python-bioblend to Debian Med team) Andreas Tille <tille@debian.org> - 2022-01-02 10:20 +0100
                            Re: Transfering packages from Debian Med to DPT (Was: Please enable  me transfering python-bioblend to Debian Med team) Andreas Tille <tille@debian.org> - 2022-01-02 11:30 +0100
                              Re: Transfering packages from Debian Med to DPT (Was: Please enable  me transfering python-bioblend to Debian Med team) Andreas Tille <tille@debian.org> - 2022-01-02 21:20 +0100
                                Re: Transfering packages from Debian Med to DPT (Was: Please enable  me transfering python-bioblend to Debian Med team) Andreas Tille <tille@debian.org> - 2022-01-03 14:40 +0100

Page 1 of 2  [1] 2  Next page →

#13786 — Please enable me transfering python-bioblend to Debian Med team

Hi,

we want to take over python-bioblend to Debian Med team.  Unfortunately
the transfer procedure requires owner permissions to remove the package
from the old place.  Could someone grant Nilesh Patra or me owner
permissions on this package?  Alternatively I can grant maintainer
permissions to some python-team owner to move the package over.

Kind regards

       Andreas.

-- 
http://fam-tille.de

[toc] | [next] | [standalone]

#13788

Ping?  Could any admin of Debian Python Team help out?  We can simply
recreate the repository in Debian Med and move on ... but that might
be confusing for users who will find two clones in differen teams.
Thank you, Andreas.

Am Sun, Dec 19, 2021 at 05:06:43PM +0100 schrieb Andreas Tille:
> Hi,
> 
> we want to take over python-bioblend to Debian Med team.  Unfortunately
> the transfer procedure requires owner permissions to remove the package
> from the old place.  Could someone grant Nilesh Patra or me owner
> permissions on this package?  Alternatively I can grant maintainer
> permissions to some python-team owner to move the package over.
> 
> Kind regards
> 
>        Andreas.
> 
> -- 
> http://fam-tille.de
> 
> 

-- 
http://fam-tille.de

[toc] | [prev] | [next] | [standalone]

#13789

[Multipart message — attachments visible in raw view] — view raw

Andreas Tille <andreas@an3as.eu> wrote on 21/12/2021 at 15:43:11+0100:

> Ping?  Could any admin of Debian Python Team help out?  We can simply
> recreate the repository in Debian Med and move on ... but that might
> be confusing for users who will find two clones in differen teams.
> Thank you, Andreas.

I'm sorry but pressuring to take over a package is not really fine. If
you're not happy with the time it takes for an answer, you can try to
fill an ITS and if the procedure goes to its end then you may take over.

Apart from that, you'll need for an admin of the team to do the transfer,
and they could be willing to check that no one in the team objects.

Steffen only did the first upload. I'd suggest to contact Ondrej (Cc-ed).

In the meantime, Nilesh is member of the Python team and therefore can
do an update of the package (but not change the maintainer).

With best regards,

-- 
PEB

[toc] | [prev] | [next] | [standalone]

#13790

Am Wed, Dec 22, 2021 at 06:13:32PM +0100 schrieb Pierre-Elliott Bécue:
> 
> Andreas Tille <andreas@an3as.eu> wrote on 21/12/2021 at 15:43:11+0100:
> 
> > Ping?  Could any admin of Debian Python Team help out?  We can simply
> > recreate the repository in Debian Med and move on ... but that might
> > be confusing for users who will find two clones in differen teams.
> > Thank you, Andreas.
> 
> I'm sorry but pressuring to take over a package is not really fine. If
> you're not happy with the time it takes for an answer, you can try to
> fill an ITS and if the procedure goes to its end then you may take over.

Please note:  The people involved are the same.  We are members of
both teams but consider the Debian Med team more appropriate.  We
are simply missing the permissions to do the move properly.
 
> Apart from that, you'll need for an admin of the team to do the transfer,
> and they could be willing to check that no one in the team objects.

Yes, we need an admin and that was I'm asking for.
 
> Steffen only did the first upload. I'd suggest to contact Ondrej (Cc-ed).
> 
> In the meantime, Nilesh is member of the Python team and therefore can
> do an update of the package (but not change the maintainer).

I'm a member myself - but the upload should happen in the Debian
Med team.  This is the point of my mail.

Kind regards

       Andreas.

-- 
http://fam-tille.de

[toc] | [prev] | [next] | [standalone]

#13791

[Multipart message — attachments visible in raw view] — view raw

Andreas Tille <tille@debian.org> wrote on 22/12/2021 at 19:42:26+0100:

> Am Wed, Dec 22, 2021 at 06:13:32PM +0100 schrieb Pierre-Elliott Bécue:
>> 
>> Andreas Tille <andreas@an3as.eu> wrote on 21/12/2021 at 15:43:11+0100:
>> 
>> > Ping?  Could any admin of Debian Python Team help out?  We can simply
>> > recreate the repository in Debian Med and move on ... but that might
>> > be confusing for users who will find two clones in differen teams.
>> > Thank you, Andreas.
>> 
>> I'm sorry but pressuring to take over a package is not really fine. If
>> you're not happy with the time it takes for an answer, you can try to
>> fill an ITS and if the procedure goes to its end then you may take over.
>
> Please note:  The people involved are the same.  We are members of
> both teams but consider the Debian Med team more appropriate.  We
> are simply missing the permissions to do the move properly.

I am aware of that.

Yet, the fact that you are members of both teams doesn't entitle you to
decide such a transfer, even if you had the technical rights to do so.

I therefore stand my point: the way Debian is made has not changed
recently, and taking over still requires a formal approval from the
maintainer, which you are not.

The only alternatives are either an ITS or MIA team orphaning their
packages, but as the maintainer is an active team, the latter will not
happen.

>> Apart from that, you'll need for an admin of the team to do the transfer,
>> and they could be willing to check that no one in the team objects.
>
> Yes, we need an admin and that was I'm asking for.

I think you missed the second part of my sentence you're quoting.

>> Steffen only did the first upload. I'd suggest to contact Ondrej (Cc-ed).
>> 
>> In the meantime, Nilesh is member of the Python team and therefore can
>> do an update of the package (but not change the maintainer).
>
> I'm a member myself - but the upload should happen in the Debian
> Med team.  This is the point of my mail.

I disagree.

Either the python team accepts the package to be transferred and it
indeed should happen there. Or you're in a hurry and you should not
change the maintainer field and still do your upload.

This probably means we should have a stanza in the DPT policy about
transfer of maintainership.

-- 
Pierre-Elliott Bécue

[toc] | [prev] | [next] | [standalone]

#13792

[Multipart message — attachments visible in raw view] — view raw

Hi Pierre-Elliot,

On Wed, Dec 22, 2021 at 08:06:01PM +0100, Pierre-Elliott Bécue wrote:
> >> I'm sorry but pressuring to take over a package is not really fine. If
> >> you're not happy with the time it takes for an answer, you can try to
> >> fill an ITS and if the procedure goes to its end then you may take over.
> >
> > Please note:  The people involved are the same.  We are members of
> > both teams but consider the Debian Med team more appropriate.  We
> > are simply missing the permissions to do the move properly.
> 
> I am aware of that.
> 
> Yet, the fact that you are members of both teams doesn't entitle you to
> decide such a transfer, even if you had the technical rights to do so.

Hmm, I am not sure what the problem in such a case would be (permission in both teams)
Steffen is the maintainer (uploader if you might prefer it that way) and he has
agreed already[1] -- so what's the problem?

[1]: https://lists.debian.org/debian-med/2021/12/msg00119.html

> I therefore stand my point: the way Debian is made has not changed
> recently, and taking over still requires a formal approval from the
> maintainer, which you are not.
> 
> The only alternatives are either an ITS or MIA team orphaning their
> packages, but as the maintainer is an active team, the latter will not
> happen.

I do not think it is sensible to take consensus from an entire team to
move a single package.
Honestly speaking, we really do not need to make team transfer 
debian processes such a high friction ones -- it just stalls the work for no good reason.
The package has not seen uploads since more than two years, I really doubt anyone in the team feels strong
ly about not moving it.

If you are talking about Ondřej doing the uploads apart from the initial uploads,
then you probably are also aware that Ondřej does a number of team-maintained package
uploads to fix bugs, does updates and so on (a lot of us do so, for that matter albeit in other teams)
I really don't think that he has a personal interest in every single one of those packages (including this one)
but we should hear from him.

> >> and they could be willing to check that no one in the team objects.

Sure but how are you making a "check" here? I do have admin access in a few teams, and speaking for
myself: I  would send out
an email to the list, wait for a time frame (maximum 1 week) and check if someone has any comments
If not, I would make a move.
So we already have a mail in the debian-python mailing list, and no objections so far, so ....

I would have probably done more to ask for consensus better (asking on IRC channels etc) but admittedly, we only
have 24 hours in the day, and several dozens of packages to do.

> I think you missed the second part of my sentence you're quoting.

I recetified this above.

> >> Steffen only did the first upload. I'd suggest to contact Ondrej (Cc-ed).
> >> 
> >> In the meantime, Nilesh is member of the Python team and therefore can
> >> do an update of the package (but not change the maintainer).
> >
> > I'm a member myself - but the upload should happen in the Debian
> > Med team.  This is the point of my mail.
> 
> I disagree.
> 
> Either the python team accepts the package to be transferred and it
> indeed should happen there. 

Please don't repeat your points. You wrote the same stuff above (wrt MIA, ITS etc)

> This probably means we should have a stanza in the DPT policy about
> transfer of maintainership.

This would be definitely helpful.

PS: I do not mean to be disrespectful, please do not interpret my reply that way, I am
only trying to reason it out.

Regards,
Nilesh

[toc] | [prev] | [next] | [standalone]

#13794

[Multipart message — attachments visible in raw view] — view raw

Nilesh Patra <nilesh@debian.org> wrote on 22/12/2021 at 20:45:53+0100:

> [[PGP Signed Part:No public key for 00BAE74B343369F1 created at 2021-12-22T20:45:49+0100 using RSA]]
> Hi Pierre-Elliot,
>
> On Wed, Dec 22, 2021 at 08:06:01PM +0100, Pierre-Elliott Bécue wrote:
>> >> I'm sorry but pressuring to take over a package is not really fine. If
>> >> you're not happy with the time it takes for an answer, you can try to
>> >> fill an ITS and if the procedure goes to its end then you may take over.
>> >
>> > Please note:  The people involved are the same.  We are members of
>> > both teams but consider the Debian Med team more appropriate.  We
>> > are simply missing the permissions to do the move properly.
>> 
>> I am aware of that.
>> 
>> Yet, the fact that you are members of both teams doesn't entitle you to
>> decide such a transfer, even if you had the technical rights to do so.
>
> Hmm, I am not sure what the problem in such a case would be (permission in both teams)
> Steffen is the maintainer (uploader if you might prefer it that way) and he has
> agreed already[1] -- so what's the problem?
>
> [1]: https://lists.debian.org/debian-med/2021/12/msg00119.html

I guess the problem is that the python-team doesn't seem to have been
Cc-ed in your exchange, which was not quoted in the initial mail of this
thread.

As I'm not subscribed to the list, it really looked like you were
intending to take over a package without any maintainer of it having
been asked for it before.

As it seems not to be the case, it's not the same at all.

>> I therefore stand my point: the way Debian is made has not changed
>> recently, and taking over still requires a formal approval from the
>> maintainer, which you are not.
>> 
>> The only alternatives are either an ITS or MIA team orphaning their
>> packages, but as the maintainer is an active team, the latter will not
>> happen.
>
> I do not think it is sensible to take consensus from an entire team to
> move a single package.

I did not suggest to wait for a consensus, but rather that an admin asks
if someone is against and waits for a reasonable delay (72 hours?) and
then makes the transfer if they're happy with it.

> Honestly speaking, we really do not need to make team transfer debian
> processes such a high friction ones -- it just stalls the work for no
> good reason.  The package has not seen uploads since more than two
> years, I really doubt anyone in the team feels strong ly about not
> moving it.

There is no real difference between teams and individual developers on
that part: a take over has to be approved or to follow due procedures,
whether we like it or not.

Here, as Steffen gave his approval, the topic is a bit moot.

> If you are talking about Ondřej doing the uploads apart from the
> initial uploads, then you probably are also aware that Ondřej does a
> number of team-maintained package uploads to fix bugs, does updates
> and so on (a lot of us do so, for that matter albeit in other teams) I
> really don't think that he has a personal interest in every single one
> of those packages (including this one) but we should hear from him.

I was under the (false) impression that Steffen was not currently
available to reply to your query. Ondřej being an admin of the team and
having done all the uploads apart from those done by Steffen, he clearly
seemed the best second contact point to ask this transfer.

>> >> and they could be willing to check that no one in the team objects.
>
> Sure but how are you making a "check" here? I do have admin access in
> a few teams, and speaking for myself: I would send out an email to the
> list, wait for a time frame (maximum 1 week) and check if someone has
> any comments If not, I would make a move.  So we already have a mail
> in the debian-python mailing list, and no objections so far, so ....
>
> I would have probably done more to ask for consensus better (asking on
> IRC channels etc) but admittedly, we only have 24 hours in the day,
> and several dozens of packages to do.

Asking globally on the list and waiting a reasonable amount of time for
a potential grunt is fine with me.

>> I think you missed the second part of my sentence you're quoting.
>
> I recetified this above.
>
>> >> Steffen only did the first upload. I'd suggest to contact Ondrej (Cc-ed).
>> >> 
>> >> In the meantime, Nilesh is member of the Python team and therefore can
>> >> do an update of the package (but not change the maintainer).
>> >
>> > I'm a member myself - but the upload should happen in the Debian
>> > Med team.  This is the point of my mail.
>> 
>> I disagree.
>> 
>> Either the python team accepts the package to be transferred and it
>> indeed should happen there. 
>
> Please don't repeat your points. You wrote the same stuff above (wrt
> MIA, ITS etc)

If many part of the same mail are raising the same point I prefer
repeating these.

>> This probably means we should have a stanza in the DPT policy about
>> transfer of maintainership.
>
> This would be definitely helpful.

> PS: I do not mean to be disrespectful, please do not interpret my
> reply that way, I am only trying to reason it out.

I don't. :)

-- 
PEB

[toc] | [prev] | [next] | [standalone]

#13866

Hi,

I think we sorted out that the request to move python-bioblend to Debian
Med is valid.  I'm CCing Debian Python team maintainers to get this
finally done.  I'm not sure whether making me the owner of that actual
repository is sufficient to enable me transfering the archive.
Alternatively I could make one of the DPT owners maintainer on Debian
Med project and let this person do the transfer.  If this is all to
complicated I'll create a new repository in Debian Med and will ask for
removal here once the package was uploaded.

Kind regards
   Andreas.

Am Wed, Dec 22, 2021 at 09:33:17PM +0100 schrieb Pierre-Elliott Bécue:
> 
> Nilesh Patra <nilesh@debian.org> wrote on 22/12/2021 at 20:45:53+0100:
> 
> > [[PGP Signed Part:No public key for 00BAE74B343369F1 created at 2021-12-22T20:45:49+0100 using RSA]]
> > Hi Pierre-Elliot,
> >
> > On Wed, Dec 22, 2021 at 08:06:01PM +0100, Pierre-Elliott Bécue wrote:
> >> >> I'm sorry but pressuring to take over a package is not really fine. If
> >> >> you're not happy with the time it takes for an answer, you can try to
> >> >> fill an ITS and if the procedure goes to its end then you may take over.
> >> >
> >> > Please note:  The people involved are the same.  We are members of
> >> > both teams but consider the Debian Med team more appropriate.  We
> >> > are simply missing the permissions to do the move properly.
> >> 
> >> I am aware of that.
> >> 
> >> Yet, the fact that you are members of both teams doesn't entitle you to
> >> decide such a transfer, even if you had the technical rights to do so.
> >
> > Hmm, I am not sure what the problem in such a case would be (permission in both teams)
> > Steffen is the maintainer (uploader if you might prefer it that way) and he has
> > agreed already[1] -- so what's the problem?
> >
> > [1]: https://lists.debian.org/debian-med/2021/12/msg00119.html
> 
> I guess the problem is that the python-team doesn't seem to have been
> Cc-ed in your exchange, which was not quoted in the initial mail of this
> thread.
> 
> As I'm not subscribed to the list, it really looked like you were
> intending to take over a package without any maintainer of it having
> been asked for it before.
> 
> As it seems not to be the case, it's not the same at all.
> 
> >> I therefore stand my point: the way Debian is made has not changed
> >> recently, and taking over still requires a formal approval from the
> >> maintainer, which you are not.
> >> 
> >> The only alternatives are either an ITS or MIA team orphaning their
> >> packages, but as the maintainer is an active team, the latter will not
> >> happen.
> >
> > I do not think it is sensible to take consensus from an entire team to
> > move a single package.
> 
> I did not suggest to wait for a consensus, but rather that an admin asks
> if someone is against and waits for a reasonable delay (72 hours?) and
> then makes the transfer if they're happy with it.
> 
> > Honestly speaking, we really do not need to make team transfer debian
> > processes such a high friction ones -- it just stalls the work for no
> > good reason.  The package has not seen uploads since more than two
> > years, I really doubt anyone in the team feels strong ly about not
> > moving it.
> 
> There is no real difference between teams and individual developers on
> that part: a take over has to be approved or to follow due procedures,
> whether we like it or not.
> 
> Here, as Steffen gave his approval, the topic is a bit moot.
> 
> > If you are talking about Ondřej doing the uploads apart from the
> > initial uploads, then you probably are also aware that Ondřej does a
> > number of team-maintained package uploads to fix bugs, does updates
> > and so on (a lot of us do so, for that matter albeit in other teams) I
> > really don't think that he has a personal interest in every single one
> > of those packages (including this one) but we should hear from him.
> 
> I was under the (false) impression that Steffen was not currently
> available to reply to your query. Ondřej being an admin of the team and
> having done all the uploads apart from those done by Steffen, he clearly
> seemed the best second contact point to ask this transfer.
> 
> >> >> and they could be willing to check that no one in the team objects.
> >
> > Sure but how are you making a "check" here? I do have admin access in
> > a few teams, and speaking for myself: I would send out an email to the
> > list, wait for a time frame (maximum 1 week) and check if someone has
> > any comments If not, I would make a move.  So we already have a mail
> > in the debian-python mailing list, and no objections so far, so ....
> >
> > I would have probably done more to ask for consensus better (asking on
> > IRC channels etc) but admittedly, we only have 24 hours in the day,
> > and several dozens of packages to do.
> 
> Asking globally on the list and waiting a reasonable amount of time for
> a potential grunt is fine with me.
> 
> >> I think you missed the second part of my sentence you're quoting.
> >
> > I recetified this above.
> >
> >> >> Steffen only did the first upload. I'd suggest to contact Ondrej (Cc-ed).
> >> >> 
> >> >> In the meantime, Nilesh is member of the Python team and therefore can
> >> >> do an update of the package (but not change the maintainer).
> >> >
> >> > I'm a member myself - but the upload should happen in the Debian
> >> > Med team.  This is the point of my mail.
> >> 
> >> I disagree.
> >> 
> >> Either the python team accepts the package to be transferred and it
> >> indeed should happen there. 
> >
> > Please don't repeat your points. You wrote the same stuff above (wrt
> > MIA, ITS etc)
> 
> If many part of the same mail are raising the same point I prefer
> repeating these.
> 
> >> This probably means we should have a stanza in the DPT policy about
> >> transfer of maintainership.
> >
> > This would be definitely helpful.
> 
> > PS: I do not mean to be disrespectful, please do not interpret my
> > reply that way, I am only trying to reason it out.
> 
> I don't. :)
> 
> -- 
> PEB



-- 
http://fam-tille.de

[toc] | [prev] | [next] | [standalone]

#13876

[Multipart message — attachments visible in raw view] — view raw

Hi Stefano/Ondřej,

On 1/11/22 8:03 PM, Andreas Tille wrote:
> Hi,
> 
> I think we sorted out that the request to move python-bioblend to Debian
> Med is valid.  I'm CCing Debian Python team maintainers to get this
> finally done.
Could you process this transfer please? Moving python-bioblend from python->med team.
You have maintainer access in -med and owner in -python, hence please consider transferring this.

Regards,
Nilesh

[toc] | [prev] | [next] | [standalone]

#13877

Hi Nilesh (2022.01.15_14:57:40_+0000)
> > I think we sorted out that the request to move python-bioblend to Debian
> > Med is valid.  I'm CCing Debian Python team maintainers to get this
> > finally done.
> Could you process this transfer please? Moving python-bioblend from python->med team.
> You have maintainer access in -med and owner in -python, hence please consider transferring this.

Transferred: https://salsa.debian.org/med-team/python-bioblend

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

[toc] | [prev] | [next] | [standalone]

#13878

Am Sat, Jan 15, 2022 at 07:23:14PM +0000 schrieb Stefano Rivera:
> > Could you process this transfer please? Moving python-bioblend from python->med team.
> > You have maintainer access in -med and owner in -python, hence please consider transferring this.
> 
> Transferred: https://salsa.debian.org/med-team/python-bioblend

Thanks a lot for moving - package is uploaded on behalf of the Debian
Med team now.
 
Kind regards

      Andreas.

-- 
http://fam-tille.de

[toc] | [prev] | [next] | [standalone]

#13793

Andreas,

On Wed, Dec 22, 2021 at 1:42 PM Andreas Tille <tille@debian.org> wrote:
>
> Am Wed, Dec 22, 2021 at 06:13:32PM +0100 schrieb Pierre-Elliott Bécue:
> >
> > Andreas Tille <andreas@an3as.eu> wrote on 21/12/2021 at 15:43:11+0100:
> >
> > > Ping?  Could any admin of Debian Python Team help out?  We can simply
> > > recreate the repository in Debian Med and move on ... but that might
> > > be confusing for users who will find two clones in differen teams.
> > > Thank you, Andreas.
> >
> > I'm sorry but pressuring to take over a package is not really fine. If
> > you're not happy with the time it takes for an answer, you can try to
> > fill an ITS and if the procedure goes to its end then you may take over.
>
> Please note:  The people involved are the same.  We are members of
> both teams but consider the Debian Med team more appropriate.  We
> are simply missing the permissions to do the move properly.

since you're talking about the appropriate team to maintain a given
package (and it seems debian-med may be more suited for bioblend), are
you also going to move all non-bio/med python packages from debian-med
to dpt? because that's the more appropriate place for things like
mypy.

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

[toc] | [prev] | [next] | [standalone]

#13795

Hi Sandro,

Am Wed, Dec 22, 2021 at 03:13:28PM -0500 schrieb Sandro Tosi:
> > Please note:  The people involved are the same.  We are members of
> > both teams but consider the Debian Med team more appropriate.  We
> > are simply missing the permissions to do the move properly.
> 
> since you're talking about the appropriate team to maintain a given
> package (and it seems debian-med may be more suited for bioblend), are
> you also going to move all non-bio/med python packages from debian-med
> to dpt? because that's the more appropriate place for things like
> mypy.

Yes, for sure.  Some packages somehow appeared for historical reasons in
Debian Med but I'm fine to move those packages you consider more
sensible in Python team (without any bureaucracy - I think for the move
into this direction I own the proper permissions). 

Feel free to make a list if there are more packages than mypy.

Kind regards

       Andreas.

-- 
http://fam-tille.de

[toc] | [prev] | [next] | [standalone]

#13799 — Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)

Hi again,

by chance I learned that I do not have permissions to create
repositories in salsa:python-team/packages thus moving packages would be
not as simple as transfering the projects.  Please grant me maintainer
permissions to enable moving packages smoothly.

Kind regards

      Andreas.

Am Wed, Dec 22, 2021 at 10:06:10PM +0100 schrieb Andreas Tille:
> Hi Sandro,
> 
> Am Wed, Dec 22, 2021 at 03:13:28PM -0500 schrieb Sandro Tosi:
> > > Please note:  The people involved are the same.  We are members of
> > > both teams but consider the Debian Med team more appropriate.  We
> > > are simply missing the permissions to do the move properly.
> > 
> > since you're talking about the appropriate team to maintain a given
> > package (and it seems debian-med may be more suited for bioblend), are
> > you also going to move all non-bio/med python packages from debian-med
> > to dpt? because that's the more appropriate place for things like
> > mypy.
> 
> Yes, for sure.  Some packages somehow appeared for historical reasons in
> Debian Med but I'm fine to move those packages you consider more
> sensible in Python team (without any bureaucracy - I think for the move
> into this direction I own the proper permissions). 
> 
> Feel free to make a list if there are more packages than mypy.
> 
> Kind regards
> 
>        Andreas.
> 
> -- 
> http://fam-tille.de
> 
> 

-- 
http://fam-tille.de

[toc] | [prev] | [next] | [standalone]

#13800 — Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)

On 12/23/21 1:54 PM, Andreas Tille wrote:
> Hi again,
> 
> by chance I learned that I do not have permissions to create
> repositories in salsa:python-team/packages thus moving packages would be
> not as simple as transfering the projects.  Please grant me maintainer
> permissions to enable moving packages smoothly.

AFAICS here[1] you do have maintainer permissions.

[1]: https://salsa.debian.org/groups/python-team/packages/-/group_members?search=tille

Regards,
Nilesh

[toc] | [prev] | [next] | [standalone]

#13802 — Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)

Hi,

Am Thu, Dec 23, 2021 at 02:07:45PM +0530 schrieb Nilesh Patra:
> On 12/23/21 1:54 PM, Andreas Tille wrote:
> > Hi again,
> > 
> > by chance I learned that I do not have permissions to create
> > repositories in salsa:python-team/packages thus moving packages would be
> > not as simple as transfering the projects.  Please grant me maintainer
> > permissions to enable moving packages smoothly.
> 
> AFAICS here[1] you do have maintainer permissions.

Hmmm, that's correct and I confirm I can create repositories manually
(just my script failed and I did not checked on salsa.)

Thus I moved mypy now and moved it to DPT[2].  Feel free to add yourself
to Uploaders and upload with the new location.

Sandro, do you have any other packages in mind?

Hope this helps

      Andreas.


[2] https://salsa.debian.org/python-team/packages/mypy/-/commit/8bca8da1ca92302b921755318d3325d53b6e0a47 

-- 
http://fam-tille.de

[toc] | [prev] | [next] | [standalone]

#13806 — Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)

> Thus I moved mypy now and moved it to DPT[2].  Feel free to add yourself
> to Uploaders and upload with the new location.

thanks!

> Sandro, do you have any other packages in mind?

too many to scan by-eyes only, so i planned on running some queries on
UDD to figure some other package out, but the udd-mirror is down, so
i'm going to provide a list (if any) later on.

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

[toc] | [prev] | [next] | [standalone]

#13807 — Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)

Hi Sandro,

Am Thu, Dec 23, 2021 at 09:52:49AM -0500 schrieb Sandro Tosi:
> > Thus I moved mypy now and moved it to DPT[2].  Feel free to add yourself
> > to Uploaders and upload with the new location.
> 
> thanks!

You are welcome.

> > Sandro, do you have any other packages in mind?
> 
> too many to scan by-eyes only, so i planned on running some queries on
> UDD to figure some other package out, but the udd-mirror is down, so
> i'm going to provide a list (if any) later on.

In general we are open to hand over general packages that are not
directly touching the medical / biological field to competent hands.  So
just ping me and I'll try to respond as quick as possible.  Please also
note:  I'd be really happy if for any of the DPT packages featuring my
ID as Uploader if somebody wants to add another ID and become an
Uploader of that package.  I have way more packages on my table than
I really want to have.

Kind regards

       Andreas.

-- 
http://fam-tille.de

[toc] | [prev] | [next] | [standalone]

#13838 — Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)

> > > Sandro, do you have any other packages in mind?
> >
> > too many to scan by-eyes only, so i planned on running some queries on
> > UDD to figure some other package out, but the udd-mirror is down, so
> > i'm going to provide a list (if any) later on.
>
> In general we are open to hand over general packages that are not
> directly touching the medical / biological field to competent hands.  So
> just ping me and I'll try to respond as quick as possible.

with UDD-mirror U&R now, i was able to generate the below list. This
is in no way a request to move them, just a potential source of data
for your consideration

arcp 0.2.1-3
    python3-arcp : (Archive and Package) URI parser and generator
enlighten 1.7.2-1
    python3-enlighten : console progress bar module for Python3
    python3-enlighten-doc : console progress bar module for Python3
(documentation)
    python3-enlighten-examples : console progress bar module for
Python3 (examples)
h5sparse 0.1.0-4
    python3-h5sparse : Scipy sparse matrix in HDF5
indexed-gzip 1.6.4-1
    python3-indexed-gzip : fast random access of gzip files in Python
pyrle 0.0.33-2
    python3-pyrle : run length arithmetic in Python
python-anndata 0.7.8-2
    python3-anndata : annotated gene by sample numpy matrix
python-avro 1.10.2+dfsg-1
    python3-avro : Apache Avro serialization system (Python 3 library)
python-ciso8601 2.2.0-1
    python3-ciso8601 : fast ISO8601 date time parser for Python written in C
python-colormap 1.0.4-2
    python3-colormap : ease manipulation of matplotlib colormaps and
color codecs (Python 3)
python-colormath 3.0.0-1.1
    python3-colormath : Abstracts common color math operations (Python
3 version)
python-cooler 0.8.11-1
    python3-cooler : library for a sparse, compressed, binary persistent storage
    python3-cooler-examples : library for a sparse, compressed, binary
persistent storage (examples)
python-depinfo 1.7.0-1
    python3-depinfo : retrieve and print Python 3 package dependencies
python-duckpy 3.2.0-2
    python3-duckpy : simple Python library for searching on DuckDuckGo
python-easydev 0.12.0+dfsg-1
    python3-easydev : common utilities to ease the development of
Python packages (Python 3)
python-etelemetry 0.2.0-4
    python3-etelemetry : lightweight Python3 client to communicate
with the etelemetry server
python-fitbit 0.3.1-2
    python-fitbit-doc : FitBit REST API Client Implementation - Documentation
    python3-fitbit : FitBit REST API Client Implementation - Python 3
python-hdmedians 0.14.2-3
    python3-hdmedians : high-dimensional medians in Python3
python-leidenalg 0.8.8-1
    python3-leidenalg : Python3 implementation of the Leiden algorithm in C++
python-lzstring 1.0.4-1.1
    python3-lzstring : LZ-based compression algorithm for Python
(Python 3 version)
python-matplotlib-venn 0.11.6-2
    python3-matplotlib-venn : Python 3 plotting area-proportional two-
and three-way Venn diagrams
python-multipletau 0.3.3+ds-3
    python-multipletau-doc : documentation for multipletau Python module
    python3-multipletau : multiple-tau algorithm for Python3/NumPy
python-multisplitby 0.0.1-4
    python3-multisplitby : Python3 module to create iterables split on
arbitrary separators
python-ncls 0.0.63+ds-1
    python3-ncls : datastructure for interval overlap queries
python-pipdeptree 2.2.0-2
    python3-pipdeptree : display dependency tree of the installed
Python 3 packages
python-pyflow 1.1.20-3
    python3-pyflow : lightweight parallel task engine for Python
python-pynndescent 0.5.2+dfsg-1
    python3-pynndescent : nearest neighbor descent for approximate
nearest neighbors
python-pypubsub 4.0.3-5
    python3-pubsub : Python 3 publish-subcribe library
python-sinfo 0.3.1-2
    python3-sinfo : print different version information for loaded modules
python-spectra 0.0.11-3
    python3-spectra : Easy color scales and color conversion for
Python (Python 3 version)
python-stdlib-list 0.8.0-4
    python3-stdlib-list : List of Python Standard Libraries (2.6-7, 3.2-9)
python-streamz 0.6.3-1
    python3-streamz : build pipelines to manage continuous streams of data
python-stubserver 1.1-2
    python3-stubserver : mock tester of external web dependencies for Python
python-tinyalign 0.2-5
    python3-tinyalign : numerical representation of differences between strings
python-typechecks 0.1.0+ds-2
    python3-typechecks : express constraints on types
python-upsetplot 0.6.0-2
    python3-upsetplot : Draw Lex et al.'s UpSet plots with Pandas and Matplotlib
python-wdlparse 0.1.0-2
    python3-wdlparse : Workflow Description Language (WDL) parser for Python
python-wordcloud 1.8.1+dfsg-2
    python3-wordcloud : little word cloud generator in Python
python-xopen 1.2.1-3
    python3-xopen : Python3 module to open compressed files transparently
smart-open 5.2.1-3
    python3-smart-open : utils for streaming large files
sorted-nearest 0.0.31+dfsg-1
    python3-sorted-nearest : Cython helper library for pyranges
sphinxcontrib-autoprogram 0.1.7-1
    python3-sphinxcontrib.autoprogram : automated documentation of CLI
programs for Sphinx (Python 3)

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

[toc] | [prev] | [next] | [standalone]

#13839 — Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)

[Multipart message — attachments visible in raw view] — view raw

Before you/someone else makes a move, some of these packages are bioinformatics
and are better suited for med team:

* indexed-gzip - This one is mainly for NIFTI image files
* python-anndata - For gene annotation
* python-fitbit - For FITBIT API (more in med domain)
* python-cooler - For genomic interaction data

There are probably more, but please do not move these ^^

Nilesh

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.maint.python

csiph-web