Re: Why does excuses list a failed autokpgtest that can never run because of unsatisfied B-D?
Andrey Rakhmatullin <[email protected]> Wed, 24 Jun 2026 13:13:06 +0500
| Newsgroups | gmane.linux.debian.devel.mentors |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Jun 23, 2026 at 06:17:33PM -0700, Soren Stoutner wrote: >The failure is simply that the Build-Dependencies cannot be satisfied on >loong64. As far as I know, they have never been satisfiable. The package is not in testing so "this is not a regression" doesn't apply. >None of the other architectures that are B-D unsatisfiable are listed as >blockers. RT doesn't require passing autopkgtests on all architectures. See ∙ ∙ Autopkgtest skipped on ppc64el: not installable (which is allowed) ∙ ∙ Autopkgtest skipped on riscv64: not installable (which is allowed) ∙ ∙ Autopkgtest skipped on s390x: not installable (which is allowed) I assume loong64 *is* required to pass for migration. -- WBR, wRAR
signature.asc
(application/pgp-signature, 894 B)
-----BEGIN PGP SIGNATURE----- iQJhBAABCgBLFiEEtf6ieDcfC1EgtGkao+OWn23e7IYFAmo7kZItFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEKPjlp9t3uyG 1TAP/236wEUqmIYOmCgeaK1c7JgFWXOO/2urmOInGDkAZIpL9WDT4XJu5DKojIT+ g9cvSaAOAVuQppX2n6OWlOfuQlNiBGC34SnriwnXXdR23D8JvX7fRgehSiny1Akj WPDRyHdgpQPGGeUTa004xhymP05r1uLfAUw1b8v8p2vZjtKSHlJEsZdXM3YXVzJz LDAfXCf3uONbwlrgCqi4g8Pcpz0z9m3cSQiYC+Zhq8+vvzBlR1wphHmMr3KFXcH4 JX787csLDxjW0/AWc60aLFMU8lXQM4hvlP487v1RX06TLkNaFiMecinS+vt9oksf X5QSl14RZfGdrqT1Do/JdfXkCAlJakaw3C8dJgltljUEL96/tIElhft1m4tdUk42 EAJZoA3KjTdZSNhS9noK38HSSayEsTlnNbTEqSppsF6ZlCbGASFsH0bUQXrRENRD W6ySKqbUTK2ZA7XWxpkGvXKniDNph+5KhhMCzJvh7CYfjADn5jpWP/vfWDzPgxz1 5nZngT11IGA3LMh/e/kzyqMMFvm85baB2pYs0tWuMGSKggB2D7UYglj3ZqDwV+rQ qN1q4LZ5PMTl0MDYvJLa+QnQvm+uYMTg1fEcnTWIKOIevM6dvv1PFwu+u/DiUxDl THJp135vhydDFzQUErkChYrVdildwi0JNAkj6/1hoCUhatIr =Ibh7 -----END PGP SIGNATURE-----