Migration blocker analysis for golang-defaults 2:1.27~0ubuntu1 in stonking-proposed:
update_excuses blocks it with "golang/amd64 in main cannot depend on golang-1.27 in universe" (and -go/-src/-doc). What happened (from https://launchpad.net/ubuntu/+source/golang-1.27/+publishinghistory): 1. golang-1.27 rc1/rc2/rc3 were auto-synced from Debian sid into stonking as universe; rc3 was later promoted to main. 2. 2026-08-24: 1.27.0-1 (final) was copied from Debian sid by hand; the copy inherited universe placement, superseding the main rc3. 3. 2026-08-25: 1.27.0-1 was briefly published in release/main and superseded back to universe ~25s later — i.e. the override machinery (per component-mismatches "movements to universe") demoted it because, per the seeds, nothing currently pulls golang-1.27 into main. And the seeds can't pull it in until golang-defaults 1.27 migrates — which britney blocks precisely because golang-1.27 is in universe. Classic transition chicken-and-egg. Resolution needed from an archive admin (same as every previous Go default transition): * Promote golang-1.27, golang-1.27-go, golang-1.27-src, golang-1.27-doc to main in stonking (justification: golang-defaults 2:1.27~0ubuntu1 in proposed, MP 509678). * Then golang-defaults migrates; the apkverifier autopkgtest blocker is already fixed in release (-11ubuntu1); the remaining jacobsa-crypto/diskv autopkgtest regressions are the FFe copy-list rows (this bug) and clear when those land (or can be hinted). After migration the seeds keep golang-1.27 in main and the auto-demoter stops fighting it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2164597 Title: FFe: Go 1.27 transition — regression fixes for reverse-build- dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/delve/+bug/2164597/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
