Dear Antonio
Apologies but I saw this too late to stop the transition to testing.
At this stage, I believe the best solution is to work on the issues in
satpy and dask; I can help.
Best regards
Alastair
On 07/12/2022 08:38, Antonio Valentino wrote:
Dear Alastair,
On Mon, 21 Nov 2022 15:12:02 +0000 Debian FTP Masters
<ftpmas...@ftp-master.debian.org> wrote:
Source: python-xarray
Source-Version: 2022.11.0-2
Done: Alastair McKinstry <mckins...@debian.org>
We believe that the bug you reported is fixed in the latest version of
python-xarray, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1022...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alastair McKinstry <mckins...@debian.org> (supplier of updated
python-xarray package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 21 Nov 2022 14:37:38 +0000
Source: python-xarray
Architecture: source
Version: 2022.11.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Alastair McKinstry <mckins...@debian.org>
Closes: 1004869 1022255 1023222
Changes:
python-xarray (2022.11.0-2) unstable; urgency=medium
.
* Ack bogs fixed in this and previous releases:
Closes: #1022255, #1004869, #1023222
Checksums-Sha1:
25bfc4ad68c46f9f7428c7a008736478f3bd2fa7 3395
python-xarray_2022.11.0-2.dsc
9d5fa48523ea38b6684f9b18e3d3a10a8aee2875 14092
python-xarray_2022.11.0-2.debian.tar.xz
Checksums-Sha256:
2921fcf4d7b5b82ed54813180ceacb2261264e99eb22e1b9bcf11e8660755e6e
3395 python-xarray_2022.11.0-2.dsc
c480af287094772516773b559ac385d6eed33001e1ded8aa1ddab4db721fc91b
14092 python-xarray_2022.11.0-2.debian.tar.xz
Files:
16ee7843761bf700d78213b6a8061f38 3395 python optional
python-xarray_2022.11.0-2.dsc
b483b08efbb572a27c4af434d3df17d1 14092 python optional
python-xarray_2022.11.0-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmN7jiUACgkQy+a7Tl2a
06Vb0Q//YmFju6NG15oqqygNRQiiGIGPXS+qvtwPbXKGJDq6g3rX24KdF2tP77i6
Aw9LjfskclEe7TRQCwaS/49qh+6CE+Tndv47nMGb3jnBGL0vYa9YqOn3XeBAHCcw
aYCvbkks5HxDWizJ6Kh2Ohef0okEl2Q/pHDKMDfF+Q8DEvGh7iFtedVF6ARquPSW
95u3V6QhCCQPws26cYPz1L2a+QJuEf49lohoVDC8u4EtaJHbv1NKXtQP1srEqf10
zqbSd6KDqT3mn4dONtF7etxzQGxSHRySEPJpXQ+2kkdmcueLUT5UAEazC6SCdCUB
GMCqMFbwi4kY7CaaK5646XxCm3QQUg3UeZAMHqsBI9gYModfKG8twRhlyA4N9mam
Unfortunately version 2022.11.2 and 2022.12.0 of xarray still causes
test failures in satpy.
According to the satpy upstream developers [1] (also reported in one
of the previous messages [2]), the problem should be related to some
kind of incompatibility between new versions of xarray and the version
of dask currently in Debian (2022.02.0).
I can confirm that updating dask to 2022.11.1 fixes the issues and
satpy tests pass with dask 2022.11.1 and xarray 2022.12.0.
I have started preparing a Merge Request [3] to update the dask package.
Unfortunately, while the Python package itself builds and works well,
it is currently not possible to build the -doc package because of
outdated build dependencies or new build dependencies still not in
debian.
In addition, there are some other test failures in satpy that are not
related to xarray/dask and could be fixed with an update to the latest
upstream version of satpy (0.38.0).
I have the packaging work done (locally), but I cannot upload until
the problem with xarray/dask is solved.
In conclusion the satpy version currently in testing works perfectly
with xarray 2022.06.0, but the migration of xarray 2022.12.0 would
break satpy and make it unbuildable both in testing and unstable.
Honestly I'm not sure about what is the best way to proceed.
In principle I think that this issue should be re-open and xarray
2022.12.0 should not migrate, for the moment at least.
But then the way forward is not clear to me.
Waiting for an update of dask could take some time.
Of course I would be more that happy to help to prepare a new version
of the dask package.
What is your idea about how to proceed?
[1] https://github.com/pytroll/satpy/issues/2248#issuecomment-1296325915
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022255#16
[3] https://salsa.debian.org/python-team/packages/dask/-/merge_requests/1
kind regards
--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
ph: +353 87 6847928 e: alast...@sceal.ie, im: @sceal.ie:mckinstry
