Bug#1090313: xarray-datatree: FTBFS: E ImportError: cannot import name 'HybridMappingProxy' from 'xarray.core.utils'

[Antonio Valentino]

Dear Santiago,

On Mon, 16 Dec 2024 17:53:21 +0000 Santiago Vila <sanvila at debian.org> wrote:
> Package: src:xarray-datatree
> Version: 0.0.14-2
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> During a rebuild of all packages in unstable, your package failed to build:
> 
> --------------------------------------------------------------------------------
> [...]
>  debian/rules binary
> dh binary --buildsystem=pybuild
>    dh_update_autotools_config -O--buildsystem=pybuild
>    dh_autoreconf -O--buildsystem=pybuild
>    dh_auto_configure -O--buildsystem=pybuild
>    dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.13 with "build" module
> I: pybuild base:311: python3.13 -m build --skip-dependency-check --no-isolation --wheel --outdir /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_datatree  
> * Building wheel...
> running bdist_wheel
> running build

[...]

> 
> The above is just how the build ends and not necessarily the most relevant part.
> If required, the full build log is available here:
> 
> https://people.debian.org/~sanvila/build-logs/202412/
> 
> About the archive rebuild: The build was made on virtual machines from AWS,
> using sbuild and a reduced chroot with only build-essential packages.
> 
> If you could not reproduce the bug please contact me privately, as I
> am willing to provide ssh access to a virtual machine where the bug is
> fully reproducible.
> 
> If this is really a bug in one of the build-depends, please use
> reassign and affects, so that this is still visible in the BTS web
> page for this package.

We plan to request the removal from the archive of xarray-datatree.

The package has been merged into xarray (2024.10) upstream and all the 
packages depending on it in the debian archive have been updated to use 
the corresponding (now) builtin feature in xarray.

The plan is to issue the request for removal as soon as all packages 
previously depending on it migrate to testing.

Please do not consider the failure as blocking.

kind regards
-- 
Antonio Valentino