Re: Suggesting change in DPT policy

+1 for this policy change too, I went through the same hurdles & thinking progress, but it's much fresher in py head because I m only contributing to DPT since 1/1/2024, doing exactly what I said I would do on my membership application mail. Before this talk happened I would not have recommended

Re: Suggesting change in DPT policy

On 3/2/24 21:29, Andreas Tille wrote: sphinxtesters (0.2.3-4) unstable; urgency=medium * Revert attempt by a rogue developer to hijack this package -- Sandro Tosi Sun, 14 Jan 2024 01:25:23 -0500 I wonder how the attribute 'rogue' is supported by the discussion above, nor where the inten

Re: Suggesting change in DPT policy

On 3/2/24 23:09, Christian Kastner wrote: Not going to name names, but I've seen this with packages I've worked on: I put a lot of effort into cleaning things up, making things robust, getting docs to build, tests to pass, collaborating with upstream, fixing reverse dependencies, and then someone

Re: Suggesting change in DPT policy

On 3/3/24 00:37, Christian Kastner wrote: For example, I also often skip tests -- it's just that I do it under conditions that I'm happy to defend (cause isolated, reported upstream, etc.), but others may not be aware of that. There are many cases where skipping tests is ok. As you wrote, when

Re: Suggesting change in DPT policy

On March 3, 2024 6:12:09 AM UTC, Andreas Tille wrote: >Hi Christian, > >Am Sat, Mar 02, 2024 at 11:48:57PM +0100 schrieb Christian Kastner: >> On 2024-03-02 23:11, Andreas Tille wrote: >> > I'm curious why you believe I didn't care. I likely would have reverted >> > my change if I didn't have m

Re: Suggesting change in DPT policy

On 2024-03-03 17:32, Thomas Goirand wrote: > On 3/3/24 00:37, Christian Kastner wrote: >> For >> example, I also often skip tests -- it's just that I do it under >> conditions that I'm happy to defend (cause isolated, reported upstream, >> etc.), but others may not be aware of that. > > There are

Help with the Cython 3.0 failures in Ceph

Hi, I'm long overdue for an upload of Ceph 18.2.x in Unstable. I'm currently stuck with the below build failure: Error compiling Cython file: ... """ name = cstr(name, 'name') cdef: rados_ioctx_t _

Re: Help with the Cython 3.0 failures in Ceph

On 3/3/24 21:08, Thomas Goirand wrote: Hi, I'm long overdue for an upload of Ceph 18.2.x in Unstable. I'm currently stuck with the below build failure: Error compiling Cython file: ...     """     name = cstr(name, 'name')