Re: Team upload policy

2021-09-16 Thread Timo Röhling
* Mattia Rizzolo [2021-09-16 17:43]: I like the science team because I always felt fine uploading random changes in the past when I needed them, in the python team I always need to ponder "will the main uploader be bothered about my chnages" every time. I was unsure about that, and I didn't

Re: Team upload policy

2021-09-16 Thread Mattia Rizzolo
On Thu, Sep 16, 2021 at 01:34:05PM +0200, Drew Parsons wrote: > The Python Team policy looks sensible to me. It is not, please do not let such thing spread outside the Python team. I don't remember if you are involved in the Python team, but I can tell you that the low-level of "teamship" that is

Re: CMake-induced breakage [was Re: Team upload policy]

2021-09-16 Thread Kyle Edwards
On Thu, Sep 16, 2021 at 6:56 AM Timo Röhling wrote: > > Hi Gard, > > * Gard Spreemann [2021-09-16 12:38]: > >Off-topic, but: where can I read about this problem? > Starting with CMake 3.19, you get a deprecation warning on stderr if > cmake_minimum_required() asks for a version below 2.8.12.

Re: Team upload policy

2021-09-16 Thread David Bremner
Drew Parsons writes: > The Python Team policy looks sensible to me. > > Any member of the team should be able to fix and upload any team package > in general. That helps spread the load and keeps the packages fresh. > > But reasonable also to have a stronger oversight model (the weak >

Re: Team upload policy

2021-09-16 Thread Drew Parsons
The Python Team policy looks sensible to me. Any member of the team should be able to fix and upload any team package in general. That helps spread the load and keeps the packages fresh. But reasonable also to have a stronger oversight model (the weak collaboration case) if a particular

CMake-induced breakage [was Re: Team upload policy]

2021-09-16 Thread Timo Röhling
Hi Gard, * Gard Spreemann [2021-09-16 12:38]: Off-topic, but: where can I read about this problem? Starting with CMake 3.19, you get a deprecation warning on stderr if cmake_minimum_required() asks for a version below 2.8.12. This will break autopkgtests unless they run with Restrictions:

Re: Team upload policy

2021-09-16 Thread Gard Spreemann
Timo Röhling writes: > fix to make the autopkgtests work again after the recent CMake upload. Off-topic, but: where can I read about this problem? -- Gard signature.asc Description: PGP signature

Team upload policy

2021-09-16 Thread Timo Röhling
Hi, I was wondering if the Science Team has a policy regarding team uploads. The reason I'm asking is that there are a few packages which need a minor fix to make the autopkgtests work again after the recent CMake upload. For example, the Python Team has an explicit rule in their team policy