[From nobody Thu Oct 29 10:21:08 2026 Received: (at submit) by bugs.debian.org; 29 Oct 2026 08:33:07 +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.2 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, 21; hammy, 150; neutral, 139; 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]:58464) 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 1xMLZL-0009In-2X for submit@bugs.debian.org; Thu, 29 Oct 2026 08:33:07 +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=J9aioIxd2E6G1BBESW4xTORJ5ab+Jy5xC8EH8nr4cIQ=; b=R3ip2P+oZJWxoKIJIpBypuCL96 5cNGV1MIue0TWEvbClpbG/WyRWQMLXQKB4V2gxpq+qqByYZG4AEi/+G2m7KXj5yCBt08f8qy29qyM 48oNeWANiGouKHMQ5QZyrrIi9vkLY8JhwddqIWfUG5TjSDQtoib/7xLJeWGr2F1buYWqnceFMLzgo x0D4cvSQA/1EAzcW2RDzJ9vlz6n4/tbg6oS7ZKlmR3X/TrxqYp8Ric7DxWYcmYihMMcw21c+QITU4 1gzrvGYmYbReb/XoZCxrm4S4EfTkqPK3JKycEBVwGZHW4M9MF4Y6DwOJltoDKJofkS4VDvJXSTP/N +6UGYKJg==; 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 1xMLZJ-002tN9-1Y for submit@bugs.debian.org; Thu, 29 Oct 2026 08:33:05 +0000 From: Paul Gevers <elbrus@debian.org> To: submit@bugs.debian.org Subject: src:jetty12: fails to migrate to testing for too long Date: Thu, 29 Oct 2026 09:07:29 +0100 Message-ID: <179326278465.44746.6611352752223835444@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: jetty12 Version: 12.0.33-1 Severity: serious Control: close -1 12.0.40-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:jetty12 has been trying to migrate for 31 days [2], hence= this bug report. The current output of the migration software for this packa= ge is copied to the bottom of this report and should list the reason why the = package is blocked. Regularly, reporting issues against reverse (build/test/r= egular) dependencies is what needs to happen. If this has already been done, = than this bug is just for tracking purposes. 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=3Djetty12 Current text from [2]: Migration status for jetty12 (12.0.33-1 to 12.0.40-1): BLOCKED: Rejected/viol= ates migration policy/introduces a regression Issues preventing migration: =E2=88=99 =E2=88=99 Autopkgtest for css-validator/0~20250226+dfsg-5: amd64: R= egression =E2=99=BB (reference =E2=99=BB), arm64: Regression =E2=99=BB (refer= ence =E2=99=BB), armhf: Regression =E2=99=BB (reference =E2=99=BB), i386: Reg= ression =E2=99=BB (reference =E2=99=BB), loong64: Regression =E2=99=BB (refer= ence =E2=99=BB), ppc64el: Regression =E2=99=BB (reference =E2=99=BB), riscv64= : Regression =E2=99=BB (reference =E2=99=BB), s390x: Regression =E2=99=BB (re= ference =E2=99=BB) =E2=88=99 =E2=88=99 Autopkgtest for vnu/26.8.15.1+dfsg-1: amd64: Regression = =E2=99=BB (reference =E2=99=BB), arm64: Regression =E2=99=BB (reference =E2= =99=BB), armhf: Regression =E2=99=BB (reference =E2=99=BB), i386: Regression = =E2=99=BB (reference =E2=99=BB), loong64: Regression =E2=99=BB (reference =E2= =99=BB), ppc64el: Regression =E2=99=BB (reference =E2=99=BB), riscv64: Regres= sion =E2=99=BB (reference =E2=99=BB), s390x: Regression =E2=99=BB (reference = =E2=99=BB) Additional info (not blocking): =E2=88=99 =E2=88=99 Piuparts tested OK - https://piuparts.debian.org/sid/sour= ce/j/jetty12.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 15 days old (needed 5 days) ]