[From nobody Mon Jun 15 14:21:12 2026
Received: (at submit) by bugs.debian.org; 17 Apr 2026 19:27:08 +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.7 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
 DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,
 SPF_HELO_NONE,SPF_NONE,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, 17; hammy, 150; neutral, 125; 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: &lt;elbrus@debian.org&gt;
Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:39520)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from &lt;elbrus@debian.org&gt;) id 1wDoqK-00Erzr-2O
 for submit@bugs.debian.org; Fri, 17 Apr 2026 19:27:08 +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=8kZGFoqW0+flXzAUV6VQ6SMn4bY/mzaicpEPAfnYTb8=; b=d7cztRv5SxRqdCgyB7Fy1pEFOF
 k4y58kx/VEmio8LCz3fe5Q0vahAzFRpocKJmkaqrybibZkw8GAGtoFfXXxkiXQbL3oSRrdgxnZVyL
 JcwZOknuiW0dH17QtP1SWFUWmli82kxgQPUfPdt0/Gk1gzO3iH2hTifqu+ETMkUH5Q5Lb99j1BFl+
 fQMqDTofywLBl+C3/H+6rhGZmG3p33XuC3foSRLd4z0ZUekmP8Wl+VxXwCdf6tPN6q1a+kaggiAOO
 KbPDyIrc3oHK2wrBrHafau4vA/vKn028koYo31wM8zzlq81Se8h3hkCLawG+O1UJhxcj7PegFaHho
 HwM1wNjQ==;
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 &lt;elbrus@debian.org&gt;) id 1wDoqJ-00FbVh-0Y
 for submit@bugs.debian.org; Fri, 17 Apr 2026 19:27:07 +0000
From: Paul Gevers &lt;elbrus@debian.org&gt;
To: submit@bugs.debian.org
Subject: src:httpcomponents-core5: fails to migrate to testing for too long
Date: Fri, 17 Apr 2026 21:27:06 +0200
Message-ID: &lt;177645402647.54739.17454001508454452719@debian.org&gt;
Content-Type: text/plain; charset=&quot;utf-8&quot;
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Debian-User: elbrus
Delivered-To: submit@bugs.debian.org

Source: httpcomponents-core5
Version: 5.4-1
Severity: serious
Control: close -1 5.4.2-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:httpcomponents-core5 has been trying to migrate for 31 da=
ys [2], hence this bug report. The current output of the migration software f=
or this package is copied to the bottom of this report and should list the re=
ason why the 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=3Dhttpcomponents-core5

Current text from [2]:
Migration status for httpcomponents-core5 (5.4-1 to 5.4.2-1): BLOCKED: Maybe =
temporary, maybe blocked but Britney is missing information (check below)
Issues preventing migration:
=E2=88=99 =E2=88=99 Missing build on all
=E2=88=99 =E2=88=99 Autopkgtest deferred: missing builds
=E2=88=99 =E2=88=99 Lintian check deferred: missing builds
Additional info (not blocking):
=E2=88=99 =E2=88=99 Piuparts tested OK - https://piuparts.debian.org/sid/sour=
ce/h/httpcomponents-core5.html
=E2=88=99 =E2=88=99 Reproduced on amd64
=E2=88=99 =E2=88=99 Reproduced on arm64
=E2=88=99 =E2=88=99 Reproduced on armhf
=E2=88=99 =E2=88=99 Reproduced on i386
=E2=88=99 =E2=88=99 Reproduced on ppc64el
=E2=88=99 =E2=88=99 31 days old (needed 5 days)
]