Re: dask.distributed RC bug #1042135
Hi Diane (and cc'ing the correct mailing list - oops!), On Fri, Aug 04, 2023 at 09:37:48AM -0700, Diane Trout wrote: > On Fri, 2023-08-04 at 14:02 +0100, Julian Gilbey wrote: > > Hi Diane, > > > > I just got emails telling me that some of my packages would be > > removed > > from testing because they (recursively) (build-)depend on > > dask.distributed: https://bugs.debian.org/1042135 > > > > Are you able to take a look at this soon, or would you like someone > > to > > do a team upload? > > > > There is also a newer version available: 2023.7.1, which may well > > resolve this. > > Last time I tried updating pyarrow wasn't properly optional and we > don't have it packaged. (And it's actually in a single repository that > builds multiple language modules) > > Dask has updated their build system some, and let me see if it'll > update. > > If I don't manage to get to it, make sure that if you try you have to > update both dask and dask.distributed together, and it's best to makes > sure that you run the dask.distributed tests using the updated dask. > > That's where why it's usually been difficult to update. Thanks so much! I see you've already started on dask :) I took at quick look at arrow - yikes! There is potentially work afoot on this though: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970021 Best wishes, Julian
Maintenance of gtts (python3-gtts)
The gtts package is, at least nominally, maintained by the Debian Python Team, but has no human uploader. As a practical matter, I think someone should either adopt it (add themselves to uploaders) or we should formally orphan the package so we aren't pretending. It has two rdepends: Reverse-Depends === * dialect [amd64 arm64 armel armhf i386 mips64el mipsel ppc64el] * mnemosyne I personally track mnemosyne, even though it's not team maintained, because i have an interest in the package. I noticed it was going to be removed from Testing because of a FTBFS bug in gtts, so I fixed gtts by updating it to the current upstream release. Looking at the upload history, it's been this way for awhile. One consequence of it not being actually maintained is that we released bookworm with a non-functional gtts package (see #1030290). If anyone had been paying attention to the package, they would have noticed that should have been an RC bug (it is now) and it would have either been fixed or removed. The package is now in not awful shape in Unstable (and barring surprises Testing later today), but it could still use some work. The major immediate task for a potential maintainer would be working with the Stable Release Managers to get bookworm fixed. If you're interested in the package and wiling to watch over it, please let me know via email. If I don't hear back, I'll assume no one is interested and orphan it in a week or two. Thanks, Scott K signature.asc Description: This is a digitally signed message part.
