[From nobody Fri May 29 10:05:07 2026 Received: (at submit) by bugs.debian.org; 20 May 2026 19:32:34 +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=-105.6 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER, SPF_HELO_NONE,SPF_PASS,UNPARSEABLE_RELAY,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, 11; hammy, 150; neutral, 124; 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: <elbrus@debian.org> Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:32984) by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from <elbrus@debian.org>) id 1wPmef-00B4qA-38 for submit@bugs.debian.org; Wed, 20 May 2026 19:32:33 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.stravinsky; h=X-Debian-User:MIME-Version:Content-Transfer-Encoding :Content-Type:Message-ID:Date:Subject:To:From:Reply-To:Cc:Content-ID: Content-Description:In-Reply-To:References; bh=XyUxekmpsX43kkbOipVZ4ecQ08u2pBcyxR/vwsQM11g=; b=LU05f3t+jT/6U+9ylNYVjVwkBc XgPgsizF4wqAPyQE6+Kxv7tn4wFB4gXbtDlIBGowAHs/gHFJhOML9MLm5Viy/B2sgG5Vft2EqQ1se 7mYIDlUBMY/hPrRfMY+hyBN0wbylGDtZ9DA0mSfGLyJV2VZGMuqOaUEJdpOuijBoyYCT+T9mOvKPc gn9StSNeHPTlnFdBZOuNYyKqDdksa9UNRd4EVVBrum6V1A71PzDuj+rJrKC1L8UUAAcSj9KHvY6ba f2NFadVcCRBhLky2JEDl6grzy3hbLZIYqa72ODW4qXyYa7XeaA3Dgrw3lEPp6gS5Yg8tstLWCEZQa wxyqhkcw==; Received: from authenticated user by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from <elbrus@debian.org>) id 1wPmee-003KjG-19 for submit@bugs.debian.org; Wed, 20 May 2026 19:32:32 +0000 From: Paul Gevers <elbrus@debian.org> To: submit@bugs.debian.org Subject: src:loggerhead: fails to migrate to testing for too long Date: Wed, 20 May 2026 21:31:16 +0200 Message-ID: <177930555152.251127.9588629831854352675@debian.org> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Debian-User: elbrus Delivered-To: submit@bugs.debian.org Source: loggerhead Version: 2.0.3-3 Severity: serious Control: close -1 2.0.3+dfsg-1 Tags: sid forky User: release.debian.org@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and = unstable for more than 30 days as having a Release Critical bug in testing [1= ]. Your package src:loggerhead has been trying to migrate for 33 days [2], he= nce this bug report. The current output of the migration software for this pa= ckage is copied to the bottom of this report and should list the reason why t= he package is blocked. If a package is out of sync between unstable and testing for a longer period,= this usually means that bugs in the package in testing cannot be fixed via u= nstable. Blocked packages can have impact on other packages, which makes prep= aring for the release more difficult. The situation that caused this bug repo= rt might even be the result of such an issue. We expect maintainers to fix is= sues that hamper the migration of their package in a timely manner. If your p= ackage in this situation due to another package, consider helping out. This bug will trigger auto-removal when appropriate. As with all new bugs, th= ere will be at least 30 days before the package is auto-removed. This bug submission immediately closes the bug with the version in unstable, = so if that version or a later version migrates, this bug will no longer affec= t testing. This bug is also tagged to only affect sid and forky, so it doesn'= t affect (old-)stable. If you believe your package is unable to migrate to testing due to issues bey= ond your control, don't hesitate to contact the Release Team. This bug report has been automatically generated. If you have any comments wi= th regards to the content or the process, please reach out to me. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html [2] https://qa.debian.org/excuses.php?package=3Dloggerhead Current text from [2]: Migration status for loggerhead (2.0.3-3 to 2.0.3+dfsg-1): BLOCKED: Rejected/= violates migration policy/introduces a regression Issues preventing migration: =E2=88=99 =E2=88=99 Updating loggerhead would introduce bugs in testing: #108= 3464 Additional info (not blocking): =E2=88=99 =E2=88=99 Piuparts tested OK - https://piuparts.debian.org/sid/sour= ce/l/loggerhead.html =E2=88=99 =E2=88=99 Reproduced on amd64 - info =E2=88=99 =E2=88=99 Reproduced on arm64 - info =E2=88=99 =E2=88=99 Reproduced on armhf - info =E2=88=99 =E2=88=99 Reproduced on i386 - info =E2=88=99 =E2=88=99 32 days old (needed 5 days) ]