Bug#1077186: fixed in lxqt-build-tools 2.0.0+really0.13.0-1
Control: reassign -1 src:lxqt-build-tools 2.0.0-1 Control: fixed -1 2.0.0+really0.13.0-1 Control: affects -1 src:lxqt-session On Thu, 01 Aug 2024 06:04:24 + Debian FTP Masters wrote: Changes: lxqt-build-tools (2.0.0+really0.13.0-1) unstable; urgency=medium . * Revert to version really0.13.0. (Closes: #1077186) Let's then also reassign this bug to the package that fixes it. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082528: src:qemu: fails to migrate to testing for too long
Source: qemu Version: 1:9.0.2+ds-2 Severity: serious Control: close -1 1:9.1.0+ds-3 Tags: sid trixie User: release.debian@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:qemu has been trying to migrate for 40 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=qemu Current text from [2]: Migration status for qemu (1:9.0.2+ds-2 to 1:9.1.0+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ autopkgtest for qemu/1:9.1.0+ds-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Failed (not a regression), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻) ∙ ∙ Built-Using: qemu gcc-14 (not considered) Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qemu.html ∙ ∙ Ignoring non-reproducibility on amd64 (not a regression) - info ♻ ∙ ∙ 15 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082527: src:django-allauth: fails to migrate to testing for too long
Source: django-allauth Version: 0.58.2-2 Severity: serious Control: close -1 64.1.0-1 Tags: sid trixie User: release.debian@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:django-allauth has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=django-allauth Current text from [2]: Migration status for django-allauth (0.58.2-2 to 64.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ autopkgtest for django-allauth/64.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass ∙ ∙ autopkgtest for django-mailman3/1.3.15-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻) Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-allauth.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 30 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082526: src:rsyslog: fails to migrate to testing for too long
Source: rsyslog Version: 8.2406.0-1 Severity: serious Control: close -1 8.2408.0-1 Tags: sid trixie User: release.debian@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:rsyslog has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=rsyslog Current text from [2]: Migration status for rsyslog (8.2406.0-1 to 8.2408.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: ∙ ∙ missing build on mips64el ∙ ∙ missing build on ppc64el ∙ ∙ arch:ppc64el not built yet, autopkgtest delayed there ∙ ∙ autopkgtest for rsyslog/8.2408.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, riscv64: Pass, s390x: Pass Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rsyslog.html ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082524: src:python-parsl: unsatisfied build dependency in testing: python3-ipyparallel
Source: python-parsl Version: 2024.08.26+ds-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082525: src:ipykernel: unsatisfied build dependency in testing: python3-ipyparallel
Source: ipykernel Version: 6.29.5-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082523: src:safe-vdash: unsatisfied build dependency in testing: librust-ratatui-0.25+default-dev
Source: safe-vdash Version: 0.17.9-3 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082422: src:m2crypto: fails to migrate to testing for too long
Source: m2crypto Version: 0.41.0+ds-3 Severity: serious Control: close -1 0.42.0-1 Tags: sid trixie User: release.debian@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:m2crypto has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=m2crypto Current text from [2]: Migration status for m2crypto (0.41.0+ds-3 to 0.42.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: ∙ ∙ missing build on armel ∙ ∙ missing build on armhf ∙ ∙ arch:armel not built yet, autopkgtest delayed there ∙ ∙ arch:armhf not built yet, autopkgtest delayed there ∙ ∙ autopkgtest for m2crypto/0.42.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/m/m2crypto.html ∙ ∙ Ignoring non-reproducibility on amd64 (not a regression) - info ♻ ∙ ∙ Ignoring non-reproducibility on arm64 (not a regression) - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082421: src:python-attrs: fails to migrate to testing for too long
Source: python-attrs Version: 23.2.0-2 Severity: serious Control: close -1 24.2.0-1 Tags: sid trixie User: release.debian@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:python-attrs has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=python-attrs Current text from [2]: Migration status for python-attrs (23.2.0-2 to 24.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ autopkgtest for python-attrs/24.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass ∙ ∙ autopkgtest for python-cattrs/23.2.3-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻) ∙ ∙ autopkgtest for python-klein/23.12.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻) Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-attrs.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082419: src:ruby-msgpack: fails to migrate to testing for too long
Source: ruby-msgpack Version: 1.4.2-2 Severity: serious Control: close -1 1.7.2-1 Tags: sid trixie User: release.debian@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:ruby-msgpack has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=ruby-msgpack Current text from [2]: Migration status for ruby-msgpack (1.4.2-2 to 1.7.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: ∙ ∙ missing build on ppc64el ∙ ∙ arch:ppc64el not built yet, autopkgtest delayed there ∙ ∙ autopkgtest for ruby-msgpack/1.7.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, riscv64: Pass, s390x: Pass Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-msgpack.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 32 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082418: src:ruby-sqlite3: fails to migrate to testing for too long
Source: ruby-sqlite3 Version: 1.6.9-1 Severity: serious Control: close -1 1.6.9-2 Tags: sid trixie User: release.debian@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:ruby-sqlite3 has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=ruby-sqlite3 Current text from [2]: Migration status for ruby-sqlite3 (1.6.9-1 to 1.6.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ autopkgtest for ruby-sqlite3/1.6.9-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻) Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-sqlite3.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082305: webkit2gtk: Please remove compiler overrides for sh4
Source: webkit2gtk Version: 2.46.0-1 Severity: normal Tags: patch User: debian-sup...@lists.debian.org Usertags: sh4 X-Debbugs-Cc: debian-sup...@lists.debian.org Hello, with GCC upstream being improved on sh4 thanks to the LRA switch [1], it's time to remove the compiler overrides for sh4 (and sh3): --- webkit2gtk-2.46.0/debian/rules.orig 2024-09-17 15:42:38.0 +0200 +++ webkit2gtk-2.46.0/debian/rules 2024-09-19 21:20:08.768120005 +0200 @@ -87,16 +87,6 @@ EXTRA_CMAKE_ARGUMENTS += -DWTF_CPU_ARM64_CORTEXA53=OFF endif -# See: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93876 -# and: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93877 -ifneq (,$(filter $(DEB_HOST_ARCH),sh3 sh4)) - CFLAGS := $(CFLAGS:-g1=-g0) - CFLAGS := $(CFLAGS:-O2=-O1) - CXXFLAGS := $(CXXFLAGS:-g1=-g0) - CXXFLAGS := $(CXXFLAGS:-O2=-O1) - CPPFLAGS += --param ggc-min-expand=10 -endif - ifneq (,$(filter noopt,$(DEB_BUILD_OPTIONS))) EXTRA_CMAKE_ARGUMENTS += -DUSE_SYSTEM_MALLOC=ON CPPFLAGS += -DRELEASE_WITHOUT_OPTIMIZATIONS Attaching a patch. Thanks, Adrian > [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 --- webkit2gtk-2.46.0/debian/rules.orig 2024-09-17 15:42:38.0 +0200 +++ webkit2gtk-2.46.0/debian/rules 2024-09-19 21:20:08.768120005 +0200 @@ -87,16 +87,6 @@ EXTRA_CMAKE_ARGUMENTS += -DWTF_CPU_ARM64_CORTEXA53=OFF endif -# See: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93876 -# and: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93877 -ifneq (,$(filter $(DEB_HOST_ARCH),sh3 sh4)) - CFLAGS := $(CFLAGS:-g1=-g0) - CFLAGS := $(CFLAGS:-O2=-O1) - CXXFLAGS := $(CXXFLAGS:-g1=-g0) - CXXFLAGS := $(CXXFLAGS:-O2=-O1) - CPPFLAGS += --param ggc-min-expand=10 -endif - ifneq (,$(filter noopt,$(DEB_BUILD_OPTIONS))) EXTRA_CMAKE_ARGUMENTS += -DUSE_SYSTEM_MALLOC=ON CPPFLAGS += -DRELEASE_WITHOUT_OPTIMIZATIONS
Bug#1081967: emscripten: cmake files expect scripts in /usr/share/emscripten to not have a suffix
Hi, On 19-09-2024 18:49, Julian Gilbey wrote: Ah! That would work. But I've now found the source of the problem, and have a suggestion for how to fix it. Shall I commit directly to the emscripten salsa repo? emscripten is QA maintained, so if you feel like you can responsibly change the package, please go ahead. I'd like to note that I also believe that the current version of emscripten also need stuff from llvm-toolchain-19 instead of 18. The autopkgtest failure of node-inwasm shows that the current version of emscripten uses a too new option --no-growable-memory 98s emcc: warning: LLVM version for clang executable "/usr/bin/clang-18" appears incorrect (seeing "18.1", expected "20") [-Wversion-check] 98s wasm-ld-18: error: unknown argument: --no-growable-memory Fixing the autopkgtest of emscripten to run in test instead of in tests and rebuilding [1] with 18 replaced by 19 in d/control shows that's not enough: """ emcc: warning: LLVM version for clang executable "/usr/bin/clang-19" appears incorrect (seeing "19.1", expected "20") [-Wversion-check] error: undefined symbol: _emscripten_tempret_set (referenced by $setTempRet0, referenced by setTempRet0, referenced by root reference (e.g. compiled C/C++ code)) warning: To disable errors for undefined symbols use `-sERROR_ON_UNDEFINED_SYMBOLS=0` warning: __emscripten_tempret_set may need to be added to EXPORTED_FUNCTIONS if it arrives from a system library Error: Aborting compilation due to previous errors emcc: error: '/usr/bin/node /usr/share/emscripten/src/compiler.mjs /tmp/tmpinds__jv.json' failed (returned 1) """ Paul [1] https://debomatic-amd64.debian.net/distribution#unstable/emscripten/3.1.66~dfsg-3~debo1/autopkgtest OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082216: patch
Here is a patch updating the checksum Description: Adapt target.dam checksum following dazzcon update daligner is now producing slightly different .dam files, so a checksum in the test suite needed to be updated. Author: Paul Mars Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082216 Bug-Ubuntu: https://bugs.launchpad.net/debian/+source/pbdagcon/+bug/2080254 Last-Update: 2024-09-19 --- diff --git a/debian/tests/run-unit-test b/debian/tests/run-unit-test index de53dfb..d110cbe 100644 --- a/debian/tests/run-unit-test +++ b/debian/tests/run-unit-test @@ -24,7 +24,7 @@ pbdagcon mapped.m5 > consensus.fasta echo "6977ed74eab5a8b58c3a90e10f1cb96c consensus.fasta" >> checksums echo "327a35213054ec8702ea35b85f3b3c44 mapped.m5" >> checksums echo "11015d691ec4d33c7ec4d8125349b739 queries.fasta" >> checksums -echo "160c2f8c3aeb52c98403c2c1c677c13e target.dam" >> checksums +echo "1f531bd449659dbd6e7d8b0e855b2f4c target.dam" >> checksums echo "63690c9bbfd08ef3ff51d040d619056a target.fasta" >> checksums md5sum --check checksums
Bug#1081967: emscripten: cmake files expect scripts in /usr/share/emscripten to not have a suffix
Hi, On Mon, 16 Sep 2024 21:44:50 +0100 Julian Gilbey wrote: Possible solutions: (1) Rename this (and presumably the other Python scripts in the same directory) without the '.py' suffix. (2) If the '.py' suffix is needed for other contexts, have a symlink to them without the '.py' suffix. (3) patch the code to find emcc in /usr/bin/ I also noticed as I was trying to debug this that two of the scripts do not have execute permission: -rw-r--r-- 1 jdg jdg 62149 Sep 8 18:10 /usr/share/emscripten/emcc.py -rw-r--r-- 1 jdg jdg 78775 Sep 8 18:10 /usr/share/emscripten/emrun.py so this will also need fixing. Upstream dropped the executable flag, so maybe it's not meant to be called directly. /usr/bin/emcc calls it as an argument to $python. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082186: src:sonic-visualiser: fails to migrate to testing for too long
Source: sonic-visualiser Version: 4.5.2-2 Severity: serious Control: close -1 5.0-1 Tags: sid trixie User: release.debian@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:sonic-visualiser has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=sonic-visualiser Current text from [2]: Migration status for sonic-visualiser (4.5.2-2 to 5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ Updating sonic-visualiser would introduce bugs in testing: #1080495 ∙ ∙ sonic-visualiser unsatisfiable Build-Depends(-Arch) on armel: qt6-pdf-dev ∙ ∙ sonic-visualiser unsatisfiable Build-Depends(-Arch) on mips64el: qt6-pdf-dev ∙ ∙ sonic-visualiser unsatisfiable Build-Depends(-Arch) on ppc64el: qt6-pdf-dev ∙ ∙ sonic-visualiser unsatisfiable Build-Depends(-Arch) on riscv64: qt6-pdf-dev ∙ ∙ sonic-visualiser unsatisfiable Build-Depends(-Arch) on s390x: qt6-pdf-dev ∙ ∙ missing build on armel ∙ ∙ missing build on mips64el ∙ ∙ missing build on ppc64el ∙ ∙ missing build on riscv64 ∙ ∙ missing build on s390x ∙ ∙ arch:armel not built yet, autopkgtest delayed there ∙ ∙ arch:ppc64el not built yet, autopkgtest delayed there ∙ ∙ arch:riscv64 not built yet, autopkgtest delayed there ∙ ∙ arch:s390x not built yet, autopkgtest delayed there Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sonic-visualiser.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082185: src:loupe: unsatisfied build dependency in testing: librust-ashpd-0.8+default-dev
Source: loupe Version: 46.2-2 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082183: src:casacore-data-sources: unsatisfied build dependency in testing: libcasa-meas7t64 | libcasa-meas7
Source: casacore-data-sources Version: 2-5 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082182: src:lomiri-indicator-network: unsatisfied build dependency in testing: ofono-dev
Source: lomiri-indicator-network Version: 1.0.2-7 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082181: src:hdf-eos4: unsatisfied build dependency in testing: libgctp-dev
Source: hdf-eos4 Version: 3.0-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1074180: php8.4 mass rebuild
Hi Athos, On 18-09-2024 22:52, Paul Gevers wrote: Well, we'd first need to add your repo to the ci.d.n infrastructure. I'll do that tomorrow. I notice that you have a new archive for (probably) each rebuild. It might be less hassle in the use of ci.d.n if you can maintain a canonical URL for your latest rebuild, e.g. a softlink from ~athos-ribeiro/rebuilds/latest to ~athos-ribeiro/rebuilds/php8.4-beta now. I've added php8.4-beta to the list of supported external repos. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082158: src:haxe: fails to migrate to testing for too long
Source: haxe Version: 1:4.3.4-2 Severity: serious Control: close -1 1:4.3.6-1 Tags: sid trixie User: release.debian@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:haxe has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=haxe Current text from [2]: Migration status for haxe (1:4.3.4-2 to 1:4.3.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck) Issues preventing migration: ∙ ∙ Build-Depends(-Arch): haxe ocaml-luv (not considered) ∙ ∙ Invalidated by build-dependency Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haxe.html ∙ ∙ autopkgtest for haxe/1:4.3.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ Required age reduced by 3 days because of autopkgtest ∙ ∙ 32 days old (needed 2 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1074180: php8.4 mass rebuild
Hi Athos, On 18-09-2024 22:47, Athos Ribeiro wrote: On Mon, Aug 26, 2024 at 08:40:31PM +0200, Paul Gevers wrote: I suppose I would need to also push php8.4 and php-defaults to that repository so autopkgtest would pick those up, right? Or is it possible to pick those from experimental? You can request from multiple additional archives, so yes, it's possible to pick those from experimental. This was also recently discussed in bug 1073983 that mentioned scripts by glondu to do the scheduling. If you're interested, that bug had more discussion so is probably a good read. I will go through that and will request those autopkgtests for the new rebuild I performed for PHP 8.4 beta available in experimental. Well, we'd first need to add your repo to the ci.d.n infrastructure. I'll do that tomorrow. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082159: src:sfst: fails to migrate to testing for too long
Source: sfst Version: 1.4.7b-1 Severity: serious Control: close -1 1.5.8-2 Tags: sid trixie User: release.debian@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:sfst has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=sfst Current text from [2]: Migration status for sfst (1.4.7b-1 to 1.5.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ Updating sfst would introduce bugs in testing: #1079107 Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sfst.html ∙ ∙ autopkgtest for sfst/1.5.8-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ Required age reduced by 3 days because of autopkgtest ∙ ∙ 32 days old (needed 7 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082160: src:golang-github-vulcand-oxy: fails to migrate to testing for too long
Source: golang-github-vulcand-oxy Version: 1.3.0-3 Severity: serious Control: close -1 2.0.0-1 Tags: sid trixie User: release.debian@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:golang-github-vulcand-oxy has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=golang-github-vulcand-oxy Current text from [2]: Migration status for golang-github-vulcand-oxy (1.3.0-3 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ autopkgtest for golang-github-vulcand-oxy/2.0.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-vulcand-oxy.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082034: src:git-delta: fails to migrate to testing for too long
Source: git-delta Version: 0.17.0-5 Severity: serious Control: close -1 0.18.0-1 Tags: sid trixie User: release.debian@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:git-delta has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=git-delta Current text from [2]: Migration status for git-delta (0.17.0-5 to 0.18.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ Updating git-delta would introduce bugs in testing: #1081864 ∙ ∙ missing build on amd64 ∙ ∙ missing build on arm64 ∙ ∙ missing build on armel ∙ ∙ missing build on armhf ∙ ∙ missing build on i386 ∙ ∙ missing build on mips64el ∙ ∙ missing build on ppc64el ∙ ∙ missing build on riscv64 ∙ ∙ missing build on s390x ∙ ∙ arch:amd64 not built yet, autopkgtest delayed there ∙ ∙ arch:arm64 not built yet, autopkgtest delayed there ∙ ∙ arch:armel not built yet, autopkgtest delayed there ∙ ∙ arch:armhf not built yet, autopkgtest delayed there ∙ ∙ arch:i386 not built yet, autopkgtest delayed there ∙ ∙ arch:ppc64el not built yet, autopkgtest delayed there ∙ ∙ arch:riscv64 not built yet, autopkgtest delayed there ∙ ∙ arch:s390x not built yet, autopkgtest delayed there Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-delta.html ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082033: src:jpy: fails to migrate to testing for too long
Source: jpy Version: 0.17.0-1 Severity: serious Control: close -1 0.18.0-1 Tags: sid trixie User: release.debian@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:jpy has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=jpy Current text from [2]: Migration status for jpy (0.17.0-1 to 0.18.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: ∙ ∙ missing build on armel ∙ ∙ missing build on mips64el ∙ ∙ arch:armel not built yet, autopkgtest delayed there Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jpy.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082031: src:mir: fails to migrate to testing for too long
Source: mir Version: 2.14.1-6 Severity: serious Control: close -1 2.14.1-7 Tags: sid trixie User: release.debian@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:mir 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=mir Current text from [2]: Migration status for mir (2.14.1-6 to 2.14.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ Updating mir would introduce bugs in testing: #1081267 ∙ ∙ missing build on arm64 ∙ ∙ missing build on armel ∙ ∙ missing build on armhf ∙ ∙ arch:arm64 not built yet, autopkgtest delayed there ∙ ∙ arch:armel not built yet, autopkgtest delayed there ∙ ∙ arch:armhf not built yet, autopkgtest delayed there ∙ ∙ autopkgtest for mir/2.14.1-7: amd64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻ (reference ♻) ∙ ∙ Build-Depends(-Arch): mir wlcs (not considered) Additional info: ∙ ∙ Updating mir will fix bugs in testing: #1075277 ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mir.html ∙ ∙ Waiting for reproducibility reference results on amd64 - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Waiting for reproducibility reference results on i386 - info ♻ ∙ ∙ 32 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082032: src:lomiri-ui-toolkit: fails to migrate to testing for too long
Source: lomiri-ui-toolkit Version: 1.3.5100+dfsg-1 Severity: serious Control: close -1 1.3.5100+dfsg-2 Tags: sid trixie User: release.debian@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:lomiri-ui-toolkit 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=lomiri-ui-toolkit Current text from [2]: Migration status for lomiri-ui-toolkit (1.3.5100+dfsg-1 to 1.3.5100+dfsg-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: ∙ ∙ missing build on armel ∙ ∙ arch:armel not built yet, autopkgtest delayed there Additional info: ∙ ∙ Updating lomiri-ui-toolkit will fix bugs in testing: #1078725 ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-ui-toolkit.html ∙ ∙ No reference result, but not reproducibility on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Ignoring non-reproducibility on i386 (not a regression) - info ♻ ∙ ∙ 32 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081892: src:twisted: fails to migrate to testing for too long
Source: twisted Version: 24.3.0-3 Severity: serious Control: close -1 24.7.0-2 Tags: sid trixie User: release.debian@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:twisted 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=twisted Current text from [2]: Migration status for twisted (24.3.0-3 to 24.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ Updating twisted would introduce bugs in testing: #1081419 ∙ ∙ autopkgtest for libervia-backend/0.9.0~hg4294-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻) ∙ ∙ autopkgtest for twisted/24.7.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/t/twisted.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 14 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081902: src:gcc-14-cross: unsatisfied build dependency in testing: libc6-dev:$host and libc6-dev-amd64-cross:$build
Source: gcc-14-cross Version: 6 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, its build dependencies can't be installed in testing (unstable has the same problem). This can also be seen on the reproducibility infrastructure [2]. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html [2] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gcc-14-cross.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081899: src:gcc-12-cross: unsatisfied build dependency in testing: libc6-dev:$host and libc6-dev-amd64-cross:$build
Source: gcc-12-cross Version: 19 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, its build dependencies can't be installed in testing (unstable has the same problem). This can also be seen on the reproducibility infrastructure [2]. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html [2] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gcc-12-cross.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081901: src:gcc-13-cross: unsatisfied build dependency in testing: libc6-dev:$host and libc6-dev-amd64-cross:$build
Source: gcc-13-cross Version: 15 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, its build dependencies can't be installed in testing (unstable has the same problem). This can also be seen on the reproducibility infrastructure [2]. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html [2] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gcc-13-cross.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081898: src:gcc-11-cross: unsatisfied build dependency in testing: libc6-dev:$host and libc6-dev-amd64-cross:$build
Source: gcc-11-cross Version: 21 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, its build dependencies can't be installed in testing (unstable has the same problem). This can also be seen on the reproducibility infrastructure [2]. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html [2] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gcc-11-cross.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081897: src:amberol: unsatisfied build dependency in testing: librust-ashpd-0.8+gtk4-dev
Source: amberol Version: 0.10.3-4 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081889: src:generate-ninja: fails to migrate to testing for too long
Source: generate-ninja Version: 0.0~git20240328.93ee9b9-1 Severity: serious Control: close -1 0.0~git20240813.54f5b53-1 Tags: sid trixie User: release.debian@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:generate-ninja has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=generate-ninja Current text from [2]: Migration status for generate-ninja (0.0~git20240328.93ee9b9-1 to 0.0~git20240813.54f5b53-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: ∙ ∙ missing build on armel ∙ ∙ missing build on armhf ∙ ∙ arch:armel not built yet, autopkgtest delayed there ∙ ∙ arch:armhf not built yet, autopkgtest delayed there ∙ ∙ autopkgtest for generate-ninja/0.0~git20240813.54f5b53-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/g/generate-ninja.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 32 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081896: src:gnome-metronome: unsatisfied build dependency in testing: librust-gtk4-0.8+v4-10-dev
Source: gnome-metronome Version: 1.3.0-5 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081895: src:gnome-snapshot: unsatisfied build dependency in testing: librust-gstreamer-0.22+default-dev
Source: gnome-snapshot Version: 46.3-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081894: src:railway-gtk: unsatisfied build dependency in testing: librust-gdk4-0.8+default-dev (>= 0.8.0-~~)
Source: railway-gtk Version: 2.4.0-4 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081893: src:rust-tiny-dfr: unsatisfied build dependency in testing: librust-cairo-rs-0.19+freetype-dev
Source: rust-tiny-dfr Version: 0.3.1-2 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081891: src:accounts-qml-module: fails to migrate to testing for too long: uploader built arch:all binary
Source: accounts-qml-module Version: 0.7+git20231028.05e79eb-1 Severity: serious Control: close -1 0.7+git20231028.05e79eb-5 Tags: sid trixie pending User: release.debian@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:accounts-qml-module has been trying to migrate for 32 days [2]. Hence, I am filing this bug. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=accounts-qml-module OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081890: src:sqlite3: fails to migrate to testing for too long
Source: sqlite3 Version: 3.46.0-1 Severity: serious Control: close -1 3.46.1-1 Tags: sid trixie User: release.debian@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:sqlite3 has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=sqlite3 Current text from [2]: Migration status for sqlite3 (3.46.0-1 to 3.46.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ autopkgtest for ruby-sqlite3/1.6.9-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻) Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqlite3.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 32 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1065416: Bastian's offer in #1065416
Hi Matthias, On Sun, 2024-09-15 at 13:50 +0200, Matthias Klose wrote: > > It is trivial for us to add support for additional architectures once > > they are minimally supported in upstream Linux (we may also require > > that dpkg recognises their triplet; I'm not sure). There is no > > requirement that we define a kernel configuration for the architecture > > at the same time, or ever (see x32). > > > > Can we assume that new Debian Linux ports will be able to satisfy that > > or would that be a problem sometimes? > > CCing Adrian, he recently wanted to provide cross toolchains for > sparc-linux-gnu and ia64-linux-gnu, which the kernel doesn't provide > anymore. So a design which allows these toolchains would be helpful. I actually don't care about ia64 anymore as the architecture was beyond repair and upstream really wanted to get rid of it. Having said that, a cross-toolchain for 32-bit SPARC would be nice to have (binutils, glibc, gcc and linux-libc-dev) to perform regular integration tests for the sparc-unknown-linux-gnu target as well as the 32-bit SPARC kernel. 32-bit SPARC has been adapted as the Leon CPU for space applications such as satellites and space craft. Thanks to this, SPARC is also being actively maintained in the Linux kernel again and there is solid funding behind the port. Oracle also has some people actively maintaining the software stack for SPARC, allegedly even on Linux although the latter doesn't have high priority at the moment. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1081542: FTBFS with Python 3.13
Source: python-greenlet Version: 2.0.2-1 Followup-For: Bug #1081542 Hello, just as a heads-up: This issue has been fixed upstream with version 3.1.0, so that this bug report can be closed once that version has been uploaded to unstable. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1066996: python-greenlet: Please add patch to support sh4
Hello, On Sat, 2024-03-16 at 18:29 +0100, John Paul Adrian Glaubitz wrote: > the attached patch adds support for building python-greenlet on sh4, it's > a modified (fixed) version that is currently open for review upstream [1]. This patch has now been merged upstream such that this bug can be closed when updating to the recently released greenlet 3.1.0 or newer. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1081636: node-undici: Please split out llhttp library into separate package
Source: node-undici Version: 5.28.4+dfsg1+~cs23.12.11-2 Severity: important Hello, while the libllhttp-dev package is being used by other packages such as libgit2, its source package, node-undici, has a transitive build dependency on NodeJS which means that libllhttp-dev can only be built on architectures where NodeJS is available. Since libllhttp-dev itself does not depend on NodeJS, it would be good if the llhttp library could be split out of the node-undici package so it can be built and used on any architecture, even where NodeJS is not available. This also eases the bootstrap process for new architectures. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1081602: src:microsocks: fails to migrate to testing for too long
Source: microsocks Version: 1.0.3-2 Severity: serious Control: close -1 1.0.4-2 Tags: sid trixie User: release.debian@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:microsocks has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=microsocks Current text from [2]: Migration status for microsocks (1.0.3-2 to 1.0.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck) Issues preventing migration: ∙ ∙ Build-Depends(-Arch): microsocks python-test-tunnel (not considered) ∙ ∙ Invalidated by build-dependency Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/m/microsocks.html ∙ ∙ autopkgtest for microsocks/1.0.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Reproducible on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ Required age reduced by 3 days because of autopkgtest ∙ ∙ 29 days old (needed 2 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081603: src:delve: fails to migrate to testing for too long
Source: delve Version: 1.22.1-1 Severity: serious Control: close -1 1.23.0-1 Tags: sid trixie User: release.debian@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:delve has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=delve Current text from [2]: Migration status for delve (1.22.1-1 to 1.23.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ autopkgtest for delve/1.23.0-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), i386: Pass Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/d/delve.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081601: src:python-skbio: fails to migrate to testing for too long
Source: python-skbio Version: 0.6.1-3 Severity: serious Control: close -1 0.6.2-1 Tags: sid trixie User: release.debian@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:python-skbio has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=python-skbio Current text from [2]: Migration status for python-skbio (0.6.1-3 to 0.6.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: ∙ ∙ missing build on mips64el ∙ ∙ missing build on ppc64el ∙ ∙ arch:ppc64el not built yet, autopkgtest delayed there ∙ ∙ autopkgtest for python-skbio/0.6.2-1: amd64: Pass, arm64: Pass, riscv64: Pass Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-skbio.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081599: src:halide: fails to migrate to testing for too long
Source: halide Version: 18.0.0-6 Severity: serious Control: close -1 18.0.0-8 Tags: sid trixie User: release.debian@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:halide 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=halide Current text from [2]: Migration status for halide (18.0.0-6 to 18.0.0-8): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: ∙ ∙ missing build on i386 ∙ ∙ arch:i386 not built yet, autopkgtest delayed there ∙ ∙ autopkgtest for halide/18.0.0-8: amd64: Pass, arm64: Pass Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/h/halide.html ∙ ∙ Ignoring non-reproducibility on amd64 (not a regression) - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ No reference result, but not reproducibility on i386 - info ♻ ∙ ∙ 7 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081600: src:rust-ring: fails to migrate to testing for too long
Source: rust-ring Version: 0.17.5-1 Severity: serious Control: close -1 0.17.8-1 Tags: sid trixie User: release.debian@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:rust-ring has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=rust-ring Current text from [2]: Migration status for rust-ring (0.17.5-1 to 0.17.8-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: ∙ ∙ missing build on i386 ∙ ∙ arch:i386 not built yet, autopkgtest delayed there ∙ ∙ autopkgtest for rust-ring/0.17.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ring.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Reproducible on armhf - info ♻ ∙ ∙ 30 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1006753: dkms modules not rebuilt on kernel upgrades with unattended upgrades
Hi all, On Wed, 6 Jul 2022 17:52:09 +0200 Jan Stibila wrote: If unattended-upgrades is upgrading packages one at the time (it seems like it) then lower layers can't properly order packages. In that case unattended-upgrades should be responsible for proper ordering. I'm new to unattended-upgrades, but the configuration has this: // Split the upgrade into the smallest possible chunks so that // they can be interrupted with SIGTERM. This makes the upgrade // a bit slower but it has the benefit that shutdown while a upgrade // is running is possible (with a small delay) //Unattended-Upgrade::MinimalSteps "true"; So, I believe that if you have: 1) dkms based packages 2) don't configure unattended-upgrades to only run before shutdown you should turn this to false. Disclaimer: I just interpret this from reading the configuration file ( /etc/apt/apt.conf.d/50unattended-upgrades) Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081534: libgit2: Switch to libllhttp-dev massively reduces installability of libgit2
Source: libgit2 Version: 1.8.1+ds-1 Severity: important User: debian-sp...@lists.debian.org Usertags: sparc64 X-Debbugs-Cc: debian-sp...@lists.debian.org Hello, libgit2 in experimental has been switched from libhttp-parser-dev to libllhttp-dev which massively reduced installability of libgit2 because the latter has a transistive dependency on nodejs which has only limited platform support. Please switch libgit2 back to libhttp-parser-dev for architectures that don't build libllhttp-dev because they don't have support for nodejs. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1080521: transition: Removing gjs and GNOME Shell from armel
Hi On 06-09-2024 17:32, Paul Gevers wrote: I also think that the faux-packages list is/can be architecture specific, so it's probably trivial to fix but adding all architectures but armel. I have made the constraints arch specific and dropped armel from the list. Looking at the current britney2 log I see that the task-pkgs-are-installable-faux is in the list for gwenview/ except for armel, so that seems to work as intended. Given [1] we should probably do the same for i386 very soon too. Paul [1] https://lists.debian.org/msgid-search/918d41dda41dff06c9f14fb3dd4111d85492316c.ca...@decadent.org.uk OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081515: gtk4: FTBFS on -ports architectures: many tests fail with --setup=wayland: Failed to open display
Hello Simon, On Thu, 2024-09-12 at 11:48 +0100, Simon McVittie wrote: > weston might be broken on all -ports architectures and functional on > all release architectures, but that level of coincidence seems a little > far-fetched. So my next theory for this is that something is consistently > different about the -ports buildds - perhaps their XDG_RUNTIME_DIR is > set up differently? - and that is causing > "debian/tests/run-with-display wayland" (or the copy of weston that it > runs) to fail? Thanks for the report. The configuration for the Debian Ports buildds is maintained via Puppet[1], the same applies to the release architectures [2]. So, if there is any relevant difference, it should be possible to find that in the Puppet configuration and make necessary changes to the Ports Puppet configuration. Adrian > [1] https://salsa.debian.org/debian-ports-team/dsa-puppet > [2] https://salsa.debian.org/dsa-team/mirror/dsa-puppet -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1081501: musescore3: Buttons too big
Package: musescore3 Version: 3.2.3+dfsg2-17 Severity: normal Dear Debian folks, Using Debian sid/unstable with *gnome-shell* 47~rc-3 from the suite *experimental*, and scaling the screen content to 200 %, the buttons are too big in MuseScore as seen in the attachment. Kind regards, Paul PS: No idea, if it’s related to other issues [1]. [1]: https://gitlab.gnome.org/GNOME/mutter/-/issues/3661
Bug#1081452: src:rust-num-complex: fails to migrate to testing for too long
Source: rust-num-complex Version: 0.4.0-2 Severity: serious Control: close -1 0.4.6-1 Tags: sid trixie User: release.debian@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:rust-num-complex has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=rust-num-complex Current text from [2]: Migration status for rust-num-complex (0.4.0-2 to 0.4.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ autopkgtest for rust-num-complex/0.4.6-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻) ∙ ∙ missing build on i386 ∙ ∙ arch:i386 not built yet, autopkgtest delayed there Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-num-complex.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Reproducible on armhf - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081450: src:cinnamon-desktop-environment: fails to migrate to testing for too long
Source: cinnamon-desktop-environment Version: 5.8.0 Severity: serious Control: close -1 6.0.1 Tags: sid trixie User: release.debian@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:cinnamon-desktop-environment has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=cinnamon-desktop-environment Current text from [2]: Migration status for cinnamon-desktop-environment (5.8.0 to 6.0.1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/cinnamon-desktop-environment.html Additional info: ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Reproducible on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 26 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081451: src:far2l: fails to migrate to testing for too long
Source: far2l Version: 2.6.2~beta+ds-1 Severity: serious Control: close -1 2.6.3~beta+ds-1 Tags: sid trixie User: release.debian@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:far2l has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=far2l Current text from [2]: Migration status for far2l (2.6.2~beta+ds-1 to 2.6.3~beta+ds-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: ∙ ∙ missing build on armel ∙ ∙ missing build on armhf ∙ ∙ arch:armel not built yet, autopkgtest delayed there ∙ ∙ arch:armhf not built yet, autopkgtest delayed there Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/f/far2l.html ∙ ∙ Ignoring non-reproducibility on amd64 (not a regression) - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Ignoring non-reproducibility on i386 (not a regression) - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081362: unblock: libdata-validate-domain-perl/0.15-1
Hi, On 11-09-2024 08:17, EiPiFun wrote: The only thing I want to confirm is that will tests be performed again if lintian is upgraded? Failing tests are retried after 1 day once the results come in. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081274: ftp.debian.org: snapper-gui wrongly removed from testing
Control: retitle -1 reverse dependencies can get autoremoved too early Control: tags -1 wontfix Hi, On Tue, 10 Sep 2024 14:24:30 +0530 Ritesh Raj Sarraf wrote: Yesterday, I got a report that snapper-gui is removed from Debian testing. The reason for removal is Debiang bug: 1073699, which is for the snapper package. snapper is still in the archive while snapper-gui has been removed. snapper has an RC bug and hence it's listed for autoremoval. All reverse dependencies of packages listed for autoremoval get also listed for autoremoval. Packages listed for autoremoval get early warnings, so it shouldn't come as a surprise that your package is removed. There's no mechanism in place to guarantee this will be done in lockstep. While it seems unfair that snapper isn't removed at the same time as snapper-gui, that's a hard to solve problem because we're using our migration software to do the autoremoval via removal hints and that process isn't designed to handle removal hints in a block. So while it's technically possible to fix this issue, I don't think anybody will spend their time on this problem any time soon. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081309: src:gnome-characters: fails to migrate to testing for too long
Source: gnome-characters Version: 46.0-1 Severity: serious Control: close -1 47~alpha-1 Tags: sid trixie User: release.debian@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:gnome-characters has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=gnome-characters Current text from [2]: Migration status for gnome-characters (46.0-1 to 47~alpha-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: ∙ ∙ missing build on mips64el Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-characters.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Reproducible on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081308: src:golang-github-anacrolix-fuse: fails to migrate to testing for too long
Source: golang-github-anacrolix-fuse Version: 0.2.0-2 Severity: serious Control: close -1 0.3.1-1 Tags: sid trixie User: release.debian@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:golang-github-anacrolix-fuse has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=golang-github-anacrolix-fuse Current text from [2]: Migration status for golang-github-anacrolix-fuse (0.2.0-2 to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ autopkgtest for golang-github-anacrolix-fuse/0.3.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-anacrolix-fuse.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 30 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081305: src:r-cran-glmmtmb: fails to migrate to testing for too long
Source: r-cran-glmmtmb Version: 1.1.8+dfsg-3 Severity: serious Control: close -1 1.1.9+dfsg-2 Tags: sid trixie User: release.debian@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:r-cran-glmmtmb 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=r-cran-glmmtmb Current text from [2]: Migration status for r-cran-glmmtmb (1.1.8+dfsg-3 to 1.1.9+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ autopkgtest for r-cran-glmmtmb/1.1.9+dfsg-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻) ∙ ∙ Depends: r-cran-glmmtmb r-cran-tmb (not considered) Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-glmmtmb.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Waiting for reproducibility test results on i386 - info ♻ ∙ ∙ 7 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081307: src:restic: fails to migrate to testing for too long
Source: restic Version: 0.16.4-2 Severity: serious Control: close -1 0.17.0-1 Tags: sid trixie User: release.debian@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:restic has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=restic Current text from [2]: Migration status for restic (0.16.4-2 to 0.17.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck) Issues preventing migration: ∙ ∙ Built-Using: restic golang-github-anacrolix-fuse (not considered) ∙ ∙ Invalidated by built-using Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/restic.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Reproducible on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 30 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081306: src:audit: fails to migrate to testing for too long
Source: audit Version: 1:3.1.2-4 Severity: serious Control: close -1 1:4.0.1-1 Tags: sid trixie User: release.debian@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:audit 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=audit Current text from [2]: Migration status for audit (1:3.1.2-4 to 1:4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ Updating audit would introduce bugs in testing: #1078810 ∙ ∙ autopkgtest for audit/1:4.0.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻) ∙ ∙ missing build on mips64el ∙ ∙ missing build on riscv64 ∙ ∙ arch:riscv64 not built yet, autopkgtest delayed there Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/a/audit.html ∙ ∙ 32 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081304: src:ruby-stackprof: fails to migrate to testing for too long
Source: ruby-stackprof Version: 0.2.25-2 Severity: serious Control: close -1 0.2.26-1 Tags: sid trixie User: release.debian@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:ruby-stackprof 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=ruby-stackprof Current text from [2]: Migration status for ruby-stackprof (0.2.25-2 to 0.2.26-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ Updating ruby-stackprof would introduce bugs in testing: #1078501, #994456 ∙ ∙ missing build on arm64 ∙ ∙ missing build on armel ∙ ∙ missing build on armhf ∙ ∙ missing build on i386 ∙ ∙ missing build on riscv64 ∙ ∙ arch:arm64 not built yet, autopkgtest delayed there ∙ ∙ arch:armel not built yet, autopkgtest delayed there ∙ ∙ arch:armhf not built yet, autopkgtest delayed there ∙ ∙ arch:i386 not built yet, autopkgtest delayed there ∙ ∙ arch:riscv64 not built yet, autopkgtest delayed there ∙ ∙ autopkgtest for ruby-stackprof/0.2.26-1: amd64: Pass, ppc64el: Pass, s390x: Pass Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-stackprof.html ∙ ∙ 32 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081121: src:cups-pk-helper: fails to migrate to testing for too long
Source: cups-pk-helper Version: 0.2.6-1 Severity: serious Control: close -1 0.2.6-2 Tags: sid trixie User: release.debian@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:cups-pk-helper has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=cups-pk-helper Current text from [2]: Migration status for cups-pk-helper (0.2.6-1 to 0.2.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ Updating cups-pk-helper would introduce bugs in testing: #1079125, #1079293 ∙ ∙ Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/cups-pk-helper.html Additional info: ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Reproducible on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081120: src:eclipse-jdt-debug: fails to migrate to testing for too long
Source: eclipse-jdt-debug Version: 4.26-1 Severity: serious Control: close -1 4.29-1 Tags: sid trixie User: release.debian@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:eclipse-jdt-debug has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=eclipse-jdt-debug Current text from [2]: Migration status for eclipse-jdt-debug (4.26-1 to 4.29-1): Waiting for another item to be ready to migrate (no action required now - check later) Issues preventing migration: ∙ ∙ Build-Depends(-Arch): eclipse-jdt-debug eclipse-jdt-core (not considered) ∙ ∙ Depends: eclipse-jdt-debug eclipse-jdt-core (not considered) ∙ ∙ Invalidated by build-dependency ∙ ∙ Invalidated by dependency ∙ ∙ Build-Depends(-Arch): eclipse-jdt-debug eclipse-jdt-ui ∙ ∙ Depends: eclipse-jdt-debug eclipse-jdt-ui Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-jdt-debug.html ∙ ∙ uninstallable on arch armel (which is allowed), not running autopkgtest there ∙ ∙ uninstallable on arch armhf (which is allowed), not running autopkgtest there ∙ ∙ uninstallable on arch i386 (which is allowed), not running autopkgtest there ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ 30 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081119: src:eclipse-jdt-ui: fails to migrate to testing for too long
Source: eclipse-jdt-ui Version: 4.26-1 Severity: serious Control: close -1 4.29-1 Tags: sid trixie User: release.debian@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:eclipse-jdt-ui has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=eclipse-jdt-ui Current text from [2]: Migration status for eclipse-jdt-ui (4.26-1 to 4.29-1): Waiting for another item to be ready to migrate (no action required now - check later) Issues preventing migration: ∙ ∙ Build-Depends(-Arch): eclipse-jdt-ui eclipse-jdt-core (not considered) ∙ ∙ Depends: eclipse-jdt-ui eclipse-jdt-core (not considered) ∙ ∙ Invalidated by build-dependency ∙ ∙ Invalidated by dependency Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-jdt-ui.html ∙ ∙ uninstallable on arch armel (which is allowed), not running autopkgtest there ∙ ∙ uninstallable on arch armhf (which is allowed), not running autopkgtest there ∙ ∙ uninstallable on arch i386 (which is allowed), not running autopkgtest there ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081117: src:r-cran-survey: fails to migrate to testing for too long
Source: r-cran-survey Version: 4.2-1-1 Severity: serious Control: close -1 4.4-2-1 Tags: sid trixie User: release.debian@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:r-cran-survey has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=r-cran-survey Current text from [2]: Migration status for r-cran-survey (4.2-1-1 to 4.4-2-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ autopkgtest for r-cran-gb2/2.1.1-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻) ∙ ∙ autopkgtest for r-cran-survey/4.4-2-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻) Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-survey.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Reproducible on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081118: src:r-cran-psychtools: fails to migrate to testing for too long
Source: r-cran-psychtools Version: 2.4.2-1 Severity: serious Control: close -1 2.4.3-1 Tags: sid trixie User: release.debian@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:r-cran-psychtools has been trying to migrate for 31 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. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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 trixie, 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 and has only been sent manually. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=r-cran-psychtools Current text from [2]: Migration status for r-cran-psychtools (2.4.2-1 to 2.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ Updating r-cran-psychtools would introduce bugs in testing: #1078401 ∙ ∙ r-cran-psychtools unsatisfiable Build-Depends(-Arch) on amd64: r-cran-rtf ∙ ∙ missing build on all ∙ ∙ arch:all not built yet, autopkgtest delayed Additional info: ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-psychtools.html ∙ ∙ Waiting for reproducibility test results on amd64 - info ♻ ∙ ∙ Waiting for reproducibility test results on arm64 - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Waiting for reproducibility test results on i386 - info ♻ ∙ ∙ 31 days old (needed 5 days) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081031: src:r-cran-smcfcs: fails to migrate to testing for too long: autopkgtest regression
Source: r-cran-smcfcs Version: 1.7.1+dfsg-1 Severity: serious Control: close -1 1.8.0+dfsg-1 Tags: sid trixie User: release.debian@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:r-cran-smcfcs has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=r-cran-smcfcs OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1081027: src:sssd: flaky autopkgtest: spawn id exp3 not open
Source: sssd Version: 2.9.5-3 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul https://ci.debian.net/packages/s/sssd/testing/amd64/51295873/ 41s The LDAP user can login on a terminal 41s + /usr/bin/expect -f debian/tests/login.exp testuser1 testuser1secret 41s spawn login 41s send: spawn id exp3 not open 41s while executing 41s "send "$user\r"" 41s (file "debian/tests/login.exp" line 21) OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072512: debci: mutter fails tests
Control: severity -1 serious Control: retitle -1 mutter: flaky autopgktest Hi, On Mon, 3 Jun 2024 10:12:07 -0400 =?UTF-8?Q?Jeremy_B=C3=ADcha?= wrote: The tests passed on retry and libxcursor is no longer blocked from migrating. Sorry that the autopkgtests are flaky. :( The ratio at which mutter (at least on amd64) is failing on ci.d.n is unacceptable. (The ratio where I'm starting to doubt about severity is about 1/6 to 1/8 failures, but recent history is more like 1/2.) Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1080521: transition: Removing gjs and GNOME Shell from armel
Hi, On 06-09-2024 15:16, Simon McVittie wrote: When we discussed this in 2022, Paul Gevers said that the release team could probably disable this check and allow task-gnome-desktop to be uninstallable on armel... I recall that we currently can't build d-i on armel anymore because there are not kernel udeb. I think we effectively said we're done with the installer on armel and hence we don't need to care about task-gnome-desktop on armel as much. I also think that the faux-packages list is/can be architecture specific, so it's probably trivial to fix but adding all architectures but armel. Let me do some checking if I got the details above correct. I'm convinced we should be able to deal with this on the Release Team side of this. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1080988: src:r-cran-pbkrtest: fails to migrate to testing for too long: new Build-Depends not ready to migrate
Hi Dirk, On 06-09-2024 15:19, Dirk Eddelbuettel wrote: If you think there is anything I could or should do let me know. I packaged the newest upstream version, and looked after its dependencies. You could check the excuses, which say: """ Issues preventing migration: Build-Depends(-Arch): r-cran-pbkrtest r-cran-doby (not considered) """ Following the link, we get to the excuses of r-cran-doby: """ Issues preventing migration: Not built on buildd: arch all binaries uploaded by edd, a new source-only upload is needed to allow migration """ Unfortunately as the text says, somebody needs to upload a source-only version because at this moment the Debian infrastructure can't do that. That somebody could be you. You could also help to get the infrastructure fixed, but as a patch for the problem exists, it seems that it needs convincing the right people which has failed until now. So probably not your cup of tea. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1080996: src:opendmarc: unsatisfied build dependency in testing: miltertest
Source: opendmarc Version: 1.4.2-5 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1080995: src:libdap: unsatisfied build dependency in testing: libpth-dev
Source: libdap Version: 3.21.0-1.1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1080994: src:grads: unsatisfied build dependency in testing: libsx-dev (>= 2.08)
Source: grads Version: 3:2.2.1-7 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1080993: src:mesa: fails to migrate to testing for too long: triggers autopkgtest issues
Source: mesa Version: 24.1.3-2 Severity: serious Control: close -1 24.2.1-4 Tags: sid trixie User: release.debian@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:mesa has been trying to migrate for 36 days [2]. Hence, I am filing this bug. The version in unstable triggers autopkgtest issues in src:kodi (segfault), njplot and openscad. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=mesa OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1080992: src:python-pyqtgraph: fails to migrate to testing for too long: new Build-Depends not ready to migate
Source: python-pyqtgraph Version: 0.13.7-1 Severity: serious Control: close -1 0.13.7-4 Tags: sid trixie User: release.debian@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:python-pyqtgraph has been trying to migrate for 32 days [2]. Hence, I am filing this bug. The version in unstable build depends on src:pyside6 which isn't ready to migrate yet. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=python-pyqtgraph OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1080991: src:rust-num-traits: fails to migrate to testing for too long: triggers autopkgtest issues
Source: rust-num-traits Version: 0.2.15-1 Severity: serious Control: close -1 0.2.19-2 Tags: sid trixie User: release.debian@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:rust-num-traits has been trying to migrate for 33 days [2]. Hence, I am filing this bug. The version in unstable triggers autopkgtest issues in rust-half and rust-merge. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=rust-num-traits OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1080990: src:ruby-optimist: fails to migrate to testing for too long: triggers autopkgtest issues
Source: ruby-optimist Version: 3.0.0-2 Severity: serious Control: close -1 3.1.0-1 Tags: sid trixie User: release.debian@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:ruby-optimist has been trying to migrate for 36 days [2]. Hence, I am filing this bug. The version in unstable triggers autopkgtest issues in src:lolcat. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=ruby-optimist OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1080989: src:rust-target: fails to migrate to testing for too long: autopkgtest regression except on amd64
Source: rust-target Version: 2.0.0-1 Severity: serious Control: close -1 2.1.0-1 Tags: sid trixie User: release.debian@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:rust-target has been trying to migrate for 38 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest except on amd64. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=rust-target OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1080988: src:r-cran-pbkrtest: fails to migrate to testing for too long: new Build-Depends not ready to migrate
Source: r-cran-pbkrtest Version: 0.5.2-2 Severity: serious Control: close -1 0.5.3-1 Tags: sid trixie User: release.debian@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:r-cran-pbkrtest has been trying to migrate for 39 days [2]. Hence, I am filing this bug. The version in unstable build depends on src:r-cran-doby which isn't ready to migrate. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=r-cran-pbkrtest OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1080987: src:pageedit: fails to migrate to testing for too long: Build-Depends not available on mips64el
Source: pageedit Version: 2.0.0+dfsg-1 Severity: serious Control: close -1 2.2.0+dfsg-1 Tags: sid trixie User: release.debian@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:pageedit has been trying to migrate for 40 days [2]. Hence, I am filing this bug. Your package fails to build on mips64el because its Build-Depends qt6-webengine-dev is not available there. You'll need to request removal of the binaries from unstable on that architecture to enable migration. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=pageedit OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1080986: src:sigil: fails to migrate to testing for too long: Build-Depends not available on mips64el
Source: sigil Version: 2.0.1+dfsg1-1 Severity: serious Control: close -1 2.2.1+dfsg-1 Tags: sid trixie User: release.debian@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:sigil has been trying to migrate for 40 days [2]. Hence, I am filing this bug. Your package fails to build on mips64el because its Build-Depends qt6-webengine-dev is not available there. You'll need to request removal of the binaries from unstable on that architecture to enable migration. 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. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. 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. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=sigil OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1074781: request-tracker5/4: autopkgtests don't work directly with new MariaDB 11.4
Control: tags -1 serious Hi, On Mon, 29 Jul 2024 00:10:42 +1200 Andrew Ruthven wrote: The issue isn't related to the mariadb package changing (the tests use SQLite), but rather that occasionally some of the tests fail. Looking at the failing tests in https://ci.debian.net/packages/r/request-tracker5 across various different triggers, they appear to be the same (or a similar) set of tests. But they fail intermittently. This happens often enough on some architectures on ci.d.n that the Release Team considers this RC. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Just like Otto did. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1080984: autopkgtest: Can we drop support for Ubuntu 20.04 and Python 3.8?
Hi, On 06-09-2024 13:50, Simon McVittie wrote: We could also consider changing the policy from "previous Debian stable" to "previous Debian stable, if still supported outside LTS", which would mean we can drop Debian 11 support now that it has moved to LTS, and rely on Debian 12 or Ubuntu 22.04, with Python 3.10: I agree with this proposal. I suggest something like: "previous Debian stable, if still managed by the Debian Release Team", or "all Debian releases managed by the Debian Release Team". Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1078854: viking: Add Appstream metainfo announcing HW support
Hi Petter, On 05-09-2024 06:56, Petter Reinholdtsen wrote: And now I have uploaded viking to the archive. Thanks. Perhaps you can convince upstream to make a new release to fix some of the crash bugs reported to the BTS? Probably just as well as anybody. I've never been in contact with upstream of viking before. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1080477: gtk4: FTBFS on mips64el with Mesa 24.2.x: GALLIUM_DRIVER=softpipe no longer works
On Wed, 2024-09-04 at 18:51 +0100, Simon McVittie wrote: > I'm doing a gtk4 build on the mips64el porterbox eberlin to assess whether > we can use the new ORCJIT llvmpipe and remove the workaround for #1010838, > but it's taking a while (mips64el machines are not fast). So far it's > looking as though we will still get quite a lot of test failures. The powerpc/ppc64 porterbox perotto.debian.net should be considerably faster than any mips64el machine we have. So, you may give it a try there as well. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1080432: debci-worker: debci update-worker should keep debootstrap.log upon failure
Package: debci-worker Version: 3.10 Severity: wishlist Hi, Currently bootstrapping riscv64 in testing fails, but the debci-setup.log ends with: """ I: Configuring ca-certificates... W: Failure while configuring base packages. This will be re-attempted up to five times. W: See /var/cache/lxc/debian/partial-testing-riscv64/debootstrap/debootstrap.log for details (possibly the package libfido2-1:riscv64 is at fault) W: Failure while configuring base packages. This will be re-attempted up to five times. W: See /var/cache/lxc/debian/partial-testing-riscv64/debootstrap/debootstrap.log for details (possibly the package libfido2-1:riscv64 is at fault) W: Failure while configuring base packages. This will be re-attempted up to five times. W: See /var/cache/lxc/debian/partial-testing-riscv64/debootstrap/debootstrap.log for details (possibly the package libfido2-1:riscv64 is at fault) W: Failure while configuring base packages. This will be re-attempted up to five times. W: See /var/cache/lxc/debian/partial-testing-riscv64/debootstrap/debootstrap.log for details (possibly the package libfido2-1:riscv64 is at fault) W: Failure while configuring base packages. This will be re-attempted up to five times. W: See /var/cache/lxc/debian/partial-testing-riscv64/debootstrap/debootstrap.log for details (possibly the package libfido2-1:riscv64 is at fault) Failed to download the rootfs, aborting. Failed to download 'debian base' failed to install debian lxc-create: autopkgtest-testing-riscv64.new: ../src/lxc/lxccontainer.c: create_run_template: 1589 Failed to create container from template lxc-create: autopkgtest-testing-riscv64.new: ../src/lxc/tools/lxc_create.c: lxc_create_main: 318 Failed to create container autopkgtest-testing-riscv64.new """ It would be nice to have the debootstrap.log around in that case. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1079842: Should debbugs be removed from unstable
On Thu, 29 Aug 2024 08:42:41 +0200 Alexandre Detiste wrote: > I know of one single other instance > at https://debbugs.gnu.org/ There are a few more Debbugs instances: * Debian: https://bugs.debian.org/ * GNU: https://debbugs.gnu.org/ * Emacs: https://debbugs.juix.org/ * x2go: https://bugs.x2go.org/ * Pari: https://pari.math.u-bordeaux.fr/Bugs/ -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1079983: src:lua-luv: autopkgtest regression on arm64: Segmentation fault
Hi, On 31-08-2024 02:48, James McCoy wrote: I wasn't able to reproduce this on amdahl. I attempted to reproduce it locally via qemu and also couldn't reproduce it there. It seems it's flaky, so might be a race condition. On 2024-08-29 I scheduled 10 runs on our infra (5 in unstable and 5 in testing) and they all failed. Today I did the same, and 1 passed. So that's 19/20 failures. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1079983: src:lua-luv: autopkgtest regression on arm64: Segmentation fault
Hi James, On 31-08-2024 02:48, James McCoy wrote: Nothing changed in the package itself since the last time it was consistently succeeding, so that implies something else broke it and wasn't caught before it migrated to testing. Correct. This can happen if the breakage is caused by something lower in the stack. For migration testing we only look at direct reverse (test) dependencies. The system isn't perfect. I wasn't able to reproduce this on amdahl. I attempted to reproduce it locally via qemu and also couldn't reproduce it there. If you want we can arrange access to a testbed where the test just ran and failed for you to inspect and "play with". Unfortunately I need to be on-line in the current scheme, so we'd need to align our availability. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1076612: libquadmath0: wrongly assumes that the storage for __float128 arguments is aligned
Hi Aurelien, On Fri, 19 Jul 2024 18:35:04 +0200 Aurelien Jarno wrote: Package: libquadmath0 Version: 14-20240330-1 Severity: serious Tags: upstream fixed-upstream Control: affects -1 evolver libc6 Control: fixed -1 libquadmath0/14-20240429-1 Control: block 1075938 by -1 ... Closing the bug as it is fixed in unstable. The version tracking > should do the rest for testing. The fixed version is earlier than the found version, which confused the BTS version tracking. Did you mean it the other way around? In any case, the BTS tells me now that this bug affects unstable and trixie which is clearly not what you intended. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1065538: bind9-libs hard-codes a dependency on libuv1
Control: found -1 1:9.18.2-1 Control: notfound -1 1:9.19.21-1 On Thu, 04 Jul 2024 16:44:20 +0200 =?UTF-8?Q?Ond=C5=99ej_Sur=C3=BD?= wrote: Version: 1:9.19.0-1 This was introduced after 9.18.2-1 in: Let's fix the meta-data then. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#929685: ca-certificates-java,default-jre-headless,openjdk-11-jre-headless: get rid of the circular dependency
Control: fixed -1 20230710 On Wed, 12 Jul 2023 12:04:07 +0200 Matthias Klose wrote: Version. 20230710 Fixed now. The BTS describes this bug still to unstable and trixie, hopefully fixing that with the above control command. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1052747: ortp: FTBFS: b64.h:293: error: unable to resolve link to 'b64::b64_encode2' for \link command (warning treated as error, aborting now)
Hi, On Thu, 19 Oct 2023 18:28:30 +0200 Dennis Filder wrote: I'm closing this as this was fixed with 1:5.2.98-1 in experimental. Reopen at will. Can we maybe have a solution in unstable/trixie too? Paul OpenPGP_signature.asc Description: OpenPGP digital signature
