Package: release.debian.org Severity: normal User: [email protected] Usertags: transition
I'd like to proceed with the PETSc 3.12 transition. The MUMPS 5.2.1 is also ready to go, but I think it might be more constructive to demonstrate via testing migration that the new petsc is stable with the old mumps than to show the new mumps is stable with the old petsc. If you'd prefer to avoid the fuss of 2 transitions, then I'd be happy to upgrade both at the same time. Note that SLEPc 3.12 transition is part of the PETSc transition. transition trackers: https://release.debian.org/transitions/html/auto-petsc.html https://release.debian.org/transitions/html/auto-slepc.html if not https://release.debian.org/transitions/html/auto-mumps.html Ben file: title = "petsc"; is_affected = .depends ~ "libpetsc-real3.11" | .depends ~ "libpetsc-real3.12"; is_good = .depends ~ "libpetsc-real3.12"; is_bad = .depends ~ "libpetsc-real3.11"; -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
