Path: csiph.com!news.mixmin.net!weretis.net!feeder8.news.weretis.net!news.usenet.ovh!news.corradoroberto.it!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Julian Gilbey Newsgroups: linux.debian.maint.python Subject: Re: python-xarray test failures Date: Mon, 28 Apr 2025 08:20:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Apr 28 06:17:12 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.198 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -4.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailing-List: archive/latest/22989 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/aA8dVdMRQ828O1tJ@d-and-j.net Approved: robomod@news.nic.it Lines: 49 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Alastair McKinstry , debian-python@lists.debian.org X-Original-Date: Mon, 28 Apr 2025 07:16:53 +0100 X-Original-Message-ID: X-Original-References: <7752061f-2302-438c-9e01-781894aa3161@debian.org> <28e0b349-2809-45f3-a19e-928bc0bd17bb@debian.org> <54405d49-e570-456d-9e6f-88bbbd2768af@debian.org> Xref: csiph.com linux.debian.maint.python:16864 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 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