Moving deepdiff to the Python Team? (and maybe taking over)

[Louis-Philippe Véronneau]

Hi!

One of the packages I maintain is currently broken by BTS 1001292 [1]
and it seems deepdiff is in need of some love.

Would you be open to moving it to the Python Team? I'd be more than
happy to update it to the latest upstream version (seems like it would
fix the bug in question). It doesn't seem like there's a VCS though, so
that might require some work on your side.

If you want, I'd also be happy to take over and maintain it in the
Python Team myself.

Happy holidays!

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001292

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Ruffin's Request to join Debian Python Team

[ruffsl]

Hello Debian Python Team,

I'd like to please join your team in order to help package a few new python
modules.
As expanded upon below, packaging these python modules will aid my end goal
in packaging my own build tool extensions.

Salsa account: ruffsl
(account is pending approval from your GitLab administrator)

I state I have read and accept the policy as published here:
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Thank you,
Ruffin White

---

I've read over the "Introduction for maintainers
" wiki page, and created a
mentors account:
"Ruffin White "

And then submitted two ITP tickets to WNPP as described here:
https://www.debian.org/devel/wnpp/

   - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002307
   - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002306

I've looked over the wiki for packing python modules and have draft repos:

   - https://gitlab.com/ruffsl/scantree
   - https://gitlab.com/ruffsl/dirhash

This is my first attempt at debian packaging, so I've tried to mimic a
simple example like this one:
https://salsa.debian.org/python-team/packages/python-tabulate
Among the things I'm unsure of are the packing of tests (autopkgtest?) and
CLI (man pages?)

Perhaps we could eventually transfer these repos to the Salsa org for
Debian Python Team?
https://salsa.debian.org/python-team/packages

Re: Bug#1002344: hy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

[Tianon Gravi]

On Wed, 22 Dec 2021 at 00:04, Lucas Nussbaum  wrote:
> Source: hy
> Version: 0.19.0-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20211220 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> ...
> If you fail to reproduce this, please provide a build log and diff it with 
> mine
> so that we can identify if something relevant changed in the meantime.

Ouch, thanks for the report.  I think the best fix for this is going
to be updating the package to the 1.0a3 upstream release (because I'm
fairly sure this is really about Hy 0.19 not actually supporting
Python 3.10 yet and the 1.0a3 release does), however that bump
includes the landmine of a complete documentation refactor that
creates a bit of a complex cycle with (the new)
https://github.com/hylang/sphinxcontrib-hydomain repository. 😞

I've played with building those together as a multiorig package (given
both the dependency cycle and that there aren't likely to be many/any
other consumers of "sphinxcontrib-hydomain" at this time), and ran
into a number of (hopefully minor?) problems, the first of which being
versioning (that repository has a tagged version, but it isn't
compatible with the latest Hy release nor the version of Sphinx in
Debian, but getting a commit that's good enough for the latter doesn't
fully resolve the former and requires further patching).

However, I'm definitely in a bit over my head here, so I'm adding
debian-python to CC hoping that perhaps someone there has some good
advice or ideas (maybe even a spare cycle or two). 🙈

My (non-functional) WIP can be found at
https://salsa.debian.org/hy-team/hy/-/compare/master...1.0a3 😇

If I bypass the Sphinx bits, I run into "INTERNALERROR> IndexError:
list index out of range" (and the full backtrace appears to all be in
non-Hy codelike pytest and "pluggy"), which I *think* is related to
funcparserlib needing to be 1.0.0a0+
(https://github.com/hylang/hy/pull/2164), but I am not certain.

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD

Re: Please enable me transfering python-bioblend to Debian Med team

[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

Re: Please enable me transfering python-bioblend to Debian Med team

[Pierre-Elliott Bécue]

Nilesh Patra  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 b

Re: Please enable me transfering python-bioblend to Debian Med team

[Sandro Tosi]

Andreas,

On Wed, Dec 22, 2021 at 1:42 PM Andreas Tille  wrote:
>
> Am Wed, Dec 22, 2021 at 06:13:32PM +0100 schrieb Pierre-Elliott Bécue:
> >
> > Andreas Tille  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

Re: Please enable me transfering python-bioblend to Debian Med team

[Nilesh Patra]

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


signature.asc
Description: PGP signature

Re: Please enable me transfering python-bioblend to Debian Med team

[Pierre-Elliott Bécue]

Andreas Tille  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  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


signature.asc
Description: PGP signature

Re: Please enable me transfering python-bioblend to Debian Med team

[Andreas Tille]

Am Wed, Dec 22, 2021 at 06:13:32PM +0100 schrieb Pierre-Elliott Bécue:
> 
> Andreas Tille  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

Re: Please enable me transfering python-bioblend to Debian Med team

[Pierre-Elliott Bécue]

Andreas Tille  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


signature.asc
Description: PGP signature