[From nobody Sun Jul 5 22:01:04 2026 Received: (at submit) by bugs.debian.org; 4 Jul 2026 11:36:48 +0000 X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02 (2024-03-25) on buxtehude.debian.org X-Spam-Level: X-Spam-Status: No, score=-107.6 required=4.0 tests=ALL_TRUSTED,BAYES_00, DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, FROMDEVELOPER,SPF_HELO_NONE,SPF_PASS,USER_IN_DKIM_WELCOMELIST autolearn=ham autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 12; hammy, 150; neutral, 52; spammy, 0. spammytokens: hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin, 0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311, 0.000-+--H*RT:311, 0.000-+--H*RT:108 Return-path: <ginggs@debian.org> Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:43758) by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from <ginggs@debian.org>) id 1wfyfw-004nMi-0o for submit@bugs.debian.org; Sat, 04 Jul 2026 11:36:48 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.stravinsky; h=X-Debian-User:Content-Type:To:Subject:Message-ID: Date:From:MIME-Version:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=u3CU7irW1K40qihtJBDf/KV+k62uRyEy2RwAIaN02ag=; b=Naq5XFEewViZpo+uDl0koxlYPI Eiht3uxg4r2SE46nnQ8GWfAeWG8x1Yq28NH4wfrIMF7AjuxHFNM9W+7R9f1DIRqp+iUJTkcAJ3lVD +gJA2mra+YPoo+zPkC6rJIC/7tnpYCnTCnekUY2tnuiKJj5B0jCIx4S5o36fFmjWCus91l4S4f74d KQGqssFzdt9DbzvlJzKqAfA5RQTS4yi/w4ETMli5i/DdVHQniVOEWv0qmOsErgFgLSiwDa0LtGkBV jo5dNIz4FA2Du5BvCzafDfsu6IwljppAyrATzT2womJ8FgKVcr38JODrAWoxNSjk/CI3iuhA0mOBO eXV2Y/Tg==; Received: from authenticated-user by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128) (Exim 4.96) (envelope-from <ginggs@debian.org>) id 1wfyfu-00A93f-27 for submit@bugs.debian.org; Sat, 04 Jul 2026 11:36:46 +0000 Received: by mail-vk1-f178.google.com with SMTP id 71dfb90a1353d-5bd9f5e2b7aso34621e0c.0 for <submit@bugs.debian.org>; Sat, 04 Jul 2026 04:36:46 -0700 (PDT) X-Gm-Message-State: AOJu0Yw+xdkWl4zgny1CgcJPbMHDrnoUM1WZFgCkS2v30ViXxVa309q9 hWZnW6i77edwMT9+52N3TFvb2bjJYp+AtT69mVrykuNwWYYVeala/gpBGMOYrNWxjz3b/zDEwIN Vtt/4RlOTsi9kgBSL8lcsRBv4/+4Jz5g= X-Received: by 2002:a05:6123:501:10b0:5bd:ae1c:afcf with SMTP id 71dfb90a1353d-5be1051f68dmr235494e0c.3.1783165005085; Sat, 04 Jul 2026 04:36:45 -0700 (PDT) MIME-Version: 1.0 From: Graham Inggs <ginggs@debian.org> Date: Sat, 4 Jul 2026 11:36:34 +0000 X-Gmail-Original-Message-ID: <CAM8zJQuqoUX6AsK4g+YROcXRCfayTzwG9QXsUYiZ7FU=fmMnqg@mail.gmail.com> X-Gm-Features: AVVi8Ce-fH7wgqx5gf7E64cc_GCZUNKEzCC1j4I6OH6cL2PVVaSLq40Q2nmElr0 Message-ID: <CAM8zJQuqoUX6AsK4g+YROcXRCfayTzwG9QXsUYiZ7FU=fmMnqg@mail.gmail.com> Subject: casacore: libcasa-python3-9 and python3-casacore need to migrate together To: Debian Bug Tracking System <submit@bugs.debian.org> Content-Type: text/plain; charset="UTF-8" X-Debian-User: ginggs Delivered-To: submit@bugs.debian.org Source: casacore Version: 3.8.0-5 Severity: serious X-Debbugs-Cc: debian-python@lists.debian.org User: debian-python@lists.debian.org Usertags: python3.14 Hi Maintainer casacore is part of the 'Python 3.14 as default' transition [1]. casacore was rebuilt in dependency level 2, and python-casacore was rebuilt in dependency level 3. Both rebuilds were done by binNMU. This is the first Python transition where autopkgtests are being run for binNMUs. Right now, the rebuilt casacore is attempting to migrate, but it is blocked by a failing autopkgtest triggered in python-casacore [2]. casacore/amd64 (3.8.0-5 to 3.8.0-5) Migration status for casacore/amd64 (3.8.0-5 to 3.8.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: It is the same for other architectures, except armhf, where autopkgtests are not currently blocking and the rebuild has already migrated. I think the reason for this is that python3-casacore has Depends: python3 (<< 3.15), python3 (>= 3.14~), so britney knows that python-casacore needs to migrate together with the updated python3-defaults, while libcasa-python3-9 (from src:casacore) only has Depends: libpython3.14 (>= 3.14.1), which is already in testing, so migration is being attempted. One could come up with a versioned Depends/Breaks scheme between libcasa-python3-9 and python3-casacore, but I think that if libcasa-python3-9 were to also Depends: python3 (<< 3.15), python3 (>= 3.14~), then britney would know that libcasa-python3-9, python3-casacore and python3-defaults all need to migrate together. Regards Graham [1] https://release.debian.org/transitions/html/python3.14-default.html [2] https://release.debian.org/britney/update_excuses.html#casacore/amd64 ]