satpy_0.59.0-1_source.changes ACCEPTED into unstable

[Sebastiaan Couwenberg]

On 12/5/25 8:24 AM, Antonio Valentino wrote:
> Il 04/12/25 09:37, Sebastiaan Couwenberg ha scritto:
>> Testing migration is blocked by autopkgtest failures, the one on riscv64 is considered a legitimate blocker, see: #1121879.
>>
>> I don't expect there to be any actual users of satpy on riscv64, so you may want to exclude these architectures from autopkgtest like pyogrio and pytroll-schedule for example.

In case you didn't notice, aurel32 provided a patch:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1121879#17

> Yeas I noticed.
> I already have a fix, I just excluded the offending test, non-critical.

Excluding tests is quite a big hammer, I know you use this often, but I'm not a fan.

I prefer pytest.mark.xfail(strict=False, reason="...") to ignore failures unconditionally, although in this case skipif would be more appropriate.

My suggestion was to add `architecture=!riscv64 !s390x` to d/t/autopkgtest-pkg-pybuild.conf to make it explicit that we don't care about tests on these architectures.

> I didn't upload because I was having some issues in building the package due to unrelated issues (not all packages are available for Python 3.14).

Yes, the timing of the python3.14-add transition is a bit unfortunate. Such is life in unstable.
  
> I will upload ASAP.
No rush.

Kind Regards,

Bas

-- 
  PGP Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1