Re: python-xarray test failures

[Julian Gilbey <julian@d-and-j.net>]

I've just uploaded -4 to unstable, which is identical to -3 in
experimental but with a new changelog entry:

python-xarray (2025.03.1-4) unstable; urgency=medium

  * Team upload
  * Push to unstable

 -- Julian Gilbey <jdg@debian.org>  Mon, 28 Apr 2025 06:43:27 +0100


Best wishes,

   Julian


On Fri, Apr 25, 2025 at 03:00:12PM +1000, Stuart Prescott wrote:
> Hi Alastair
> 
> Thanks for working on these failing tests.
> 
> I'm not sure that the uploads are going where you intend, however:
> 
> $ grep ^python-xarray debian/changelog | head -2 | tac
> python-xarray (2025.03.1-2) experimental; urgency=medium
> python-xarray (2025.03.1-3) unstable; urgency=medium
> 
> $ rmadison -s unstable,experimental python-xarray
> python-xarray | 2025.03.1-2   | unstable     | source
> python-xarray | 2025.03.1-3   | experimental | source
> 
> that is, the upload for unstable went to experimental, and the upload for
> experimental went to unstable. (btw I think this is the sort of thing that
> lintian will point out if you run it against the .changes file)
> 
> That also means that these changes haven't fixed the underlying issue: CI
> for 2025.03.1-2 is still failing on multiple architectures (and there are no
> changes in 2025.03.1-3).
> 
> regards
> 
> Stuart
> 
> 
> 
> -- 
> Stuart Prescott   http://www.nanonanonano.net/ stuart@nanonanonano.net
> Debian Developer  http://www.debian.org/       stuart@debian.org
> GPG fingerprint   90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7