#1151957 src:curl: fails to migrate to testing for too long

#1151957#5
Date:
2026-10-25 08:22:40 UTC
From:
To:
[Manual note on top of the template: you set urgency: high. If you need
help getting security updates to testing, don't hesitate to contact the
Release Team].

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:curl has been trying to migrate for 33
days [2], hence this bug report. The current output of the migration
software for this package 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/regular) 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 unstable. Blocked packages can have impact on other packages,
which makes preparing for the release more difficult. The situation that
caused this bug report might even be the result of such an issue. We
expect maintainers to fix issues that hamper the migration of their
package in a timely manner. If your package in this situation due to
another package, consider helping out.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there 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 affect 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 beyond your control, don't hesitate to contact the Release Team.

This bug report has been automatically generated. If you have any
comments with 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=curl

Current text from [2]:
Migration status for curl (8.22.0-1 to 8.23.0-1): BLOCKED:
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ Autopkgtest for asterisk/1:22.10.1+dfsg+~cs6.17.60671434-1: amd64:
Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test
triggered (failure will be ignored)
∙ ∙ Autopkgtest for cockpit/368-1: arm64: Pass ♻, armhf: Pass ♻
(reference ♻), i386: Pass ♻, ppc64el: Pass ♻, s390x: Pass ♻ (reference ♻)
∙ ∙ Autopkgtest for cockpit-machines/357-1: arm64: Pass ♻, armhf: No
tests, superficial or marked flaky ♻ (reference ♻), i386: No tests,
superficial or marked flaky ♻, ppc64el: Pass ♻, s390x: Pass ♻ (reference ♻)
∙ ∙ Autopkgtest for cockpit-podman/131-1: arm64: Pass ♻, armhf: Pass ♻
(reference ♻), i386: Pass ♻, ppc64el: Pass ♻, s390x: Pass ♻ (reference ♻)
∙ ∙ Autopkgtest for curl/8.23.0-1: amd64: Regression ♻ (reference ♻),
arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻),
i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻),
s390x: Regression ♻ (reference ♻)
∙ ∙ Autopkgtest for dracut: amd64: Test triggered (failure will be
ignored), arm64: Test triggered (failure will be ignored), armhf: Test
triggered (failure will be ignored), i386: Test triggered (failure will
be ignored), ppc64el: Test triggered (failure will be ignored), s390x:
Test triggered (failure will be ignored)
∙ ∙ Autopkgtest for git-annex/10.20251029-1: i386: Pass ♻
∙ ∙ Autopkgtest for ldap-rest/0.17.1-1: i386: Pass ♻
∙ ∙ Autopkgtest for libnginx-mod-http-cache-purge/1:3.0.3-1: i386: Pass ♻
∙ ∙ Autopkgtest for libnginx-mod-js/1.0.1-1: i386: Pass ♻
∙ ∙ Autopkgtest for libreoffice/4:26.8.1.1-3: amd64: Pass, arm64: Test
triggered (failure will be ignored), armhf: Test triggered (failure will
be ignored), i386: Test triggered (failure will be ignored), ppc64el:
Pass, s390x: Pass
∙ ∙ Autopkgtest for nginx/1.30.4-8: i386: Pass ♻ (reference ♻)
∙ ∙ Autopkgtest for privoxy/4.2.0-1: i386: Pass ♻ (reference ♻)
∙ ∙ Autopkgtest for ruby-curb/1.4.0-1: i386: Regression ♻ (reference ♻)
∙ ∙ Autopkgtest for slurm-wlm/26.05.4-1: arm64: Failed (not a
regression) ♻ (reference ♻), armhf: Failed (not a regression) ♻
(reference ♻), i386: Pass ♻ (reference ♻), ppc64el: Failed (not a
regression) ♻ (reference ♻), s390x: Failed (not a regression) ♻
(reference ♻)
∙ ∙ Autopkgtest for squid-deb-proxy/0.9.3: arm64: Pass ♻, armhf: Pass ♻
(reference ♻), i386: Pass ♻, ppc64el: Pass ♻, s390x: Pass ♻ (reference ♻)
∙ ∙ Missing build on riscv64
∙ ∙ Autopkgtest deferred on riscv64: missing arch:riscv64 build
∙ ∙ Lintian check waiting for test results on riscv64 - info
Additional info (not blocking):
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/c/curl.html
∙ ∙ Reproduced on amd64 - info
∙ ∙ Reproduced on arm64 - info
∙ ∙ Reproduced on armhf - info
∙ ∙ Reproduced on i386 - info
∙ ∙ 11 days old (needed 2 days)

#1151957#16
Date:
2026-10-28 19:03:26 UTC
From:
To:
Hi,

Ping. I'm surprised to not see any action or that you contacted us. If
you're waiting for the build on riscv64, I can also help with that.

Paul