Re: Policy About Maintainer and Uploaders Fields (was: PAPT: join request)

2019-11-08 Thread Utkarsh Gupta
Hey,

On 09/11/19 2:42 am, Louis-Philippe Véronneau wrote:
> On 19-11-08 16 h 01, Thomas Goirand wrote:
>> Hi intri!
>>
>> I'm very glad to count you as a member of the team! Welcome. [1]
>> I'd be glad if more perl team members join, it's so much always a
>> pleasure to meet you at each debconf.
>>
>> On 11/8/19 8:54 AM, intrigeri wrote:
>>>  - In https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin,
>>>the "Policy About Maintainer and Uploaders Fields" section
>>>mentions an "unwritten policy". Said policy seems to have been
>>>written since:
>>>
>>> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
>> It's probably time to revisit this policy. I've heard many voices
>> telling that a package should either be in the team, or just not, and I
>> very much agree with this. This middle-ground makes no sense.
> We now have a proper way to propose updates to the policy [1]!

I am not sure where we stand on the following idea, but I'd like to see
it float across.

Something I'd like to propose is to have more *owners* than just 5 of them.
Just having 5 people in the team who everyone relies on for being
granted access doesn't seem like a very nice idea to me. Whilst they are
doing a nice job, I feel every DD[1] should be able to grant access.
I don't quite like how the access is just limited to 5 people throughout
debian-python.

[1]: we can come up with some other metric to bump ACL level, too, but
we should *definitely* come up with something. One way forward is to add
DDs as owner and every other person as a maintainer. Suggestions open.


Best,
Utkarsh




signature.asc
Description: OpenPGP digital signature


Re: Policy About Maintainer and Uploaders Fields (was: PAPT: join request)

2019-11-08 Thread Louis-Philippe Véronneau
On 19-11-08 16 h 01, Thomas Goirand wrote:
> Hi intri!
> 
> I'm very glad to count you as a member of the team! Welcome. [1]
> I'd be glad if more perl team members join, it's so much always a
> pleasure to meet you at each debconf.
> 
> On 11/8/19 8:54 AM, intrigeri wrote:
>>  - In https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin,
>>the "Policy About Maintainer and Uploaders Fields" section
>>mentions an "unwritten policy". Said policy seems to have been
>>written since:
>>
>> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
> 
> It's probably time to revisit this policy. I've heard many voices
> telling that a package should either be in the team, or just not, and I
> very much agree with this. This middle-ground makes no sense.

We now have a proper way to propose updates to the policy [1]!

Once the DPMT and the PAPT teams have been merged (see [2]), we will
have to clean up the Python Team's wikis. I guess it would also be a
good time to revisit things like that "unwritten" policy :)

[1]:
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#L154

[2]:
https://salsa.debian.org/python-team/tools/python-modules/merge_requests/10

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



signature.asc
Description: OpenPGP digital signature


Re: Policy About Maintainer and Uploaders Fields (was: PAPT: join request)

2019-11-08 Thread Thomas Goirand
Hi intri!

I'm very glad to count you as a member of the team! Welcome. [1]
I'd be glad if more perl team members join, it's so much always a
pleasure to meet you at each debconf.

On 11/8/19 8:54 AM, intrigeri wrote:
>  - In https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin,
>the "Policy About Maintainer and Uploaders Fields" section
>mentions an "unwritten policy". Said policy seems to have been
>written since:
>
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

It's probably time to revisit this policy. I've heard many voices
telling that a package should either be in the team, or just not, and I
very much agree with this. This middle-ground makes no sense.

Cheers,

Thomas Goirand (zigo)

[1] I have no admin rights to add you, but welcome anyways...



Re: [Help] graphlan: Python2 removal in sid/bullseye

2019-11-08 Thread Scott Talbert

On Fri, 8 Nov 2019, Andreas Tille wrote:


Hi,

I started an attempt to port graphlan to Python3 in Git[1] but its
autopkgtest throws errors:



Running test script ./IBD_biogeography/run.sh .
Traceback (most recent call last):
 File "/usr/bin/graphlan_annotate", line 26, in 
   from src.graphlan_lib import CircTree as CTree
 File "/usr/share/graphlan/src/graphlan_lib.py", line 99, in 
   legal_options = 
set(zip(*clade_attr+ext_attr+int_attr+structural_attr+global_graphical_attr+branch_attr+leg_attr)[0])
 | set(['class'])
TypeError: 'zip' object is not subscriptable
Traceback (most recent call last):
 File "/usr/bin/graphlan", line 29, in 
   from src.graphlan_lib import CircTree as CTree
 File "/usr/share/graphlan/src/graphlan_lib.py", line 99, in 
   legal_options = 
set(zip(*clade_attr+ext_attr+int_attr+structural_attr+global_graphical_attr+branch_attr+leg_attr)[0])
 | set(['class'])
TypeError: 'zip' object is not subscriptable


Try converting the zip(x) to list(zip(x)).

See: 
https://stackoverflow.com/questions/27431390/typeerror-zip-object-is-not-subscriptable/27431433


Scott



[Help] graphlan: Python2 removal in sid/bullseye

2019-11-08 Thread Andreas Tille
Hi,

I started an attempt to port graphlan to Python3 in Git[1] but its
autopkgtest throws errors:



Running test script ./IBD_biogeography/run.sh .
Traceback (most recent call last):
  File "/usr/bin/graphlan_annotate", line 26, in 
from src.graphlan_lib import CircTree as CTree
  File "/usr/share/graphlan/src/graphlan_lib.py", line 99, in 
legal_options = 
set(zip(*clade_attr+ext_attr+int_attr+structural_attr+global_graphical_attr+branch_attr+leg_attr)[0])
 | set(['class'])
TypeError: 'zip' object is not subscriptable
Traceback (most recent call last):
  File "/usr/bin/graphlan", line 29, in 
from src.graphlan_lib import CircTree as CTree
  File "/usr/share/graphlan/src/graphlan_lib.py", line 99, in 
legal_options = 
set(zip(*clade_attr+ext_attr+int_attr+structural_attr+global_graphical_attr+branch_attr+leg_attr)[0])
 | set(['class'])
TypeError: 'zip' object is not subscriptable



Any hint how to fix this?

Kind regards

   Andreas.


[1] https://salsa.debian.org/med-team/graphlan

-- 
http://fam-tille.de