Re: Bug#1022571: transition: pandas 1.3 -> 1.5

2023-01-25 Thread Andreas Tille
Hi Graham, Am Wed, Jan 25, 2023 at 02:28:37PM +0200 schrieb Graham Inggs: > On Wed, 25 Jan 2023 at 11:43, Andreas Tille wrote: > > I was motivated for this patch by Diane's statement on the Debian Med > > matrix channel that dask and dask.distributed are interconnected. If > > the autopkgtest

Re: Bug#1022571: transition: pandas 1.3 -> 1.5

2023-01-25 Thread Graham Inggs
Hi Rebecca, Andreas On Wed, 25 Jan 2023 at 11:43, Andreas Tille wrote: > I was motivated for this patch by Diane's statement on the Debian Med > matrix channel that dask and dask.distributed are interconnected. If > the autopkgtest on Salsa CI[4] would have passed I would have uploaded. We

Re: Bug#1022571: transition: pandas 1.3 -> 1.5

2023-01-25 Thread Andreas Tille
Hi Graham Am Tue, Jan 24, 2023 at 12:50:41PM +0200 schrieb Graham Inggs: > > On Tue, 24 Jan 2023 at 00:16, Rebecca N. Palmer > wrote: > > The remaining autopkgtest failures blocking pandas are: > > - dipy/amd64 and snakemake/i386 look like random flakiness: please retry > > them. (I think DMs

Re: Bug#1022571: transition: pandas 1.3 -> 1.5

2023-01-24 Thread Graham Inggs
Hi Rebecca On Tue, 24 Jan 2023 at 00:16, Rebecca N. Palmer wrote: > The remaining autopkgtest failures blocking pandas are: > - dipy/amd64 and snakemake/i386 look like random flakiness: please retry > them. (I think DMs can't use the self-service interface.) Or for dipy, > see #1029533 for a

Re: Bug#1022571: transition: pandas 1.3 -> 1.5

2023-01-23 Thread Rebecca N. Palmer
The remaining autopkgtest failures blocking pandas are: - dipy/amd64 and snakemake/i386 look like random flakiness: please retry them. (I think DMs can't use the self-service interface.) Or for dipy, see #1029533 for a possible fix. - python-xarray/i386 looks like xarray not pandas: see

Re: Bug#1022571: transition: pandas 1.3 -> 1.5

2023-01-09 Thread Rebecca N. Palmer
skbio is fixed, ulmo is maybe fixed but untested. dask is unclear (see #1027254 for details): it looks like it's probably fixable, but I don't have an actual working fix yet. There has been no response from its maintainers.