Source: mesa
Version: 26.1.6-1
Severity: serious
Control: close -1 26.2.4-1
Tags: sid forky
User: [email protected]
Usertags: out-of-sync
Dear maintainer(s),
[Manual note to the template below: spirv-llvm-translator-22 has never
been in testing and has 2 RC bugs, can it be avoided? Otherwise, those
RC bugs need fixing before mesa can migrate.]
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:mesa has been trying to migrate for 32
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=mesa
Current text from [2]:
Migration status for mesa (26.1.6-1 to 26.2.4-1): BLOCKED:
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ Autopkgtest for gtk4/4.24.0+ds-2: i386: Pass ♻
∙ ∙ Autopkgtest for mesa/26.2.4-1: amd64: No tests, superficial or
marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf:
No tests, superficial or marked flaky ♻, i386: No tests, superficial or
marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻,
riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x:
No tests, superficial or marked flaky ♻ (reference ♻)
∙ ∙ Autopkgtest for muffin/6.6.3-1: i386: No tests, superficial or
marked flaky ♻
∙ ∙ Autopkgtest for openscad/2021.01-14: amd64: Regression ♻ (reference
♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻),
ppc64el: Pass, riscv64: Regression ♻ (reference ♻), s390x: Regression ♻
(reference ♻)
∙ ∙ Autopkgtest for phoc/0.58~alpha1-1: i386: No tests, superficial or
marked flaky ♻
∙ ∙ Build-Depends(-Arch): mesa spirv-llvm-translator-22 (not considered)
∙ ∙ Depends: mesa spirv-llvm-translator-22 (not considered)
Additional info (not blocking):
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mesa.html
∙ ∙ Not reproduced on amd64 (not a regression): mesa-libgallium,
mesa-opencl-icd, mesa-vulkan-drivers
∙ ∙ Not reproduced on arm64 (not a regression): mesa-libgallium,
mesa-opencl-icd, mesa-teflon-delegate, mesa-vulkan-drivers
∙ ∙ Not reproduced on armhf (not a regression): mesa-libgallium,
mesa-opencl-icd, mesa-vulkan-drivers
∙ ∙ Not reproduced on i386 (not a regression): mesa-libgallium,
mesa-opencl-icd, mesa-vulkan-drivers
∙ ∙ 9 days old (needed 5 days)
