[From nobody Tue Sep 8 02:07:10 2026 Received: (at submit) by bugs.debian.org; 7 Sep 2026 05:50:45 +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, 14; hammy, 150; neutral, 137; 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]:48580) 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 1x3SFh-005M6m-1o for submit@bugs.debian.org; Mon, 07 Sep 2026 05:50:45 +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=JOl6pmGPm/IKijwVK8ut6YWrpPNrSZT71f3MCAk08fY=; b=hnc53jRRJHq6Ur5PLnEbsnbrPW GRxzD5fs0Orb/FawfStJsVRF27gGMQUyAT8cTrPKejwZkuAAdWcB90LBNvjEjkyOJkcZU3lZkxuIC ZD8CPiPU+yLWoBWijnhTgXxemivz+dDBSRCDHNAx0LUreX42geX3Duh986AVpCAhDnBcFQTx8RuZ5 RtTtibpdWl/z4h30LGTMIrz+M1oAGjcu9T5/MIIEtD8KBdgZzxSZuESbXAb6d2PPhh/keGwQ6aIYL zCkPuvQCHc53TGUEHjEhn0b1nqphFFeW0nrp/RI4jdjBhUHMLvp9M23SmUowIzPqJcDG4lgnaw/RK wcRlX4wA==; 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 1x3SFf-001IBy-2v for submit@bugs.debian.org; Mon, 07 Sep 2026 05:50:44 +0000 From: Paul Gevers <elbrus@debian.org> To: submit@bugs.debian.org Subject: src:php-fig-log-test: fails to migrate to testing for too long Date: Mon, 07 Sep 2026 07:47:51 +0200 Message-ID: <178876024298.18654.4967303361242794592@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: php-fig-log-test Version: 1.1.0-4 Severity: serious Control: close -1 1.2.1-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:php-fig-log-test has been trying to migrate for 31 days [= 2], hence this bug report. The current output of the migration software for t= his package is copied to the bottom of this report and should list the reason= why the package is blocked. Regularly, reporting issues against reverse (bui= ld/test/regular) dependencies is what needs to happen. If this has already be= en 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=3Dphp-fig-log-test Current text from [2]: Migration status for php-fig-log-test (1.1.0-4 to 1.2.1-1): BLOCKED: Rejected= /violates migration policy/introduces a regression Issues preventing migration: =E2=88=99 =E2=88=99 Autopkgtest for php-fig-log-test/1.2.1-1: amd64: Regressi= on =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: Regressi= on =E2=99=BB (reference =E2=99=BB), ppc64el: Regression =E2=99=BB (reference = =E2=99=BB), riscv64: 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/p/php-fig-log-test.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 30 days old (needed 5 days) ]