Bug#1072783: src:aardvark-dns: fails to migrate to testing for too long: unstatifiable Depends on s390x
Source: aardvark-dns Version: 1.4.0-5 Severity: serious Control: close -1 1.4.0-5.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:aardvark-dns has been trying to migrate for 36 days [2]. Hence, I am filing this bug. The version in unstable can't be installed on s390x while it can in testing. 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=aardvark-dns OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072780: src:transaction: fails to migrate to testing for too long: uploader built arch:all binary
Source: transaction Version: 3.0.0-1 Severity: serious Control: close -1 4.0-1 X-Debugs-CC: alexandre.deti...@gmail.com 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:transaction has been trying to migrate for 40 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=transaction OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072779: src:golang-golang-x-tools: fails to migrate to testing for too long: triggers autopkgtest issues
Source: golang-golang-x-tools Version: 1:0.19.0+ds-1 Severity: serious Control: close -1 1:0.20.0+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:golang-golang-x-tools has been trying to migrate for 41 days [2]. Hence, I am filing this bug. The version triggers autopkgtest issues in ycmd. 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=golang-golang-x-tools OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072650: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on armel, armhf, i386 and riscv64
Source: quantlib-swig Version: 1.33-1 Severity: serious Control: close -1 1.34-1 Tags: sid trixie ftbfs 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:quantlib-swig has been trying to migrate for 40 days [2]. Hence, I am filing this bug. The version in unstable failed to build on armel, armhf, i386 and riscv64. 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=quantlib-swig OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072648: src:survival: fails to migrate to testing for too long: triggers autopkgtest issues
Source: survival Version: 3.5-8-1 Severity: serious Control: close -1 3.6-4-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:survival has been trying to migrate for 40 days [2]. Hence, I am filing this bug. The version in unstable triggers autopkgtest failure in r-cran-popepi. 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=survival OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072647: src:openttd: fails to migrate to testing for too long: FTBFS on armel and unresolved RC bug
Source: openttd Version: 13.4-1 Severity: serious Control: close -1 14.0-1 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1070208 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:openttd has been trying to migrate for 42 days [2]. Hence, I am filing this bug. The version in unstable failed to build on armel and has an unresolved RC bug: 1070208. 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=openttd OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072646: src:rust-synstructure: fails to migrate to testing for too long
Source: rust-synstructure Version: 0.12.3-2 Severity: serious Control: close -1 0.13.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:rust-synstructure has been trying to migrate for 42 days [2]. Hence, I am filing this bug. The version in unstable isn't installable. 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-synstructure OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072110: glslang breaks shaderc autopkgtest: undefined reference: ABI breakage?? -- not the case
Hi, On 01-06-2024 5:05 p.m., Philippe SWARTVAGHER wrote: As I understand it (but I can be wrong), the current state of glslang and shaderc in unstable is correct; mixing versions from testing and unstable triggers bugs that are now fixed in unstable. Ok. Does that mean that the version of glslang in unstable "Breaks" the version of shaderc in testing more than the version of glslang in testing, but it's shaderc that is broken either way? On that understanding I have manually triggered the combined test and the packages should migrate. Please close this bug if my understanding above was correct. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072535: puma: flaky autopkgtest
Source: puma Version: 6.4.2-4 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package because it showed up as regression for glibc. I noticed that it regularly fails. This particularly on happens on amd64, where our host is used to run many tests in parallel, so this may be a race condition under load. 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/p/puma/testing/amd64/47272763/ 189s 1) Error: 189s TestPluginSystemd#test_systemd_notify_usr2_hot_restart_cluster: 189s Errno::EPIPE: Broken pipe 189s /tmp/autopkgtest-lxc.7lvlk_yq/downtmp/build.uxb/src/test/test_plugin_systemd.rb:90:in `write' 189s /tmp/autopkgtest-lxc.7lvlk_yq/downtmp/build.uxb/src/test/test_plugin_systemd.rb:90:in `assert_restarts_with_systemd' 189s /tmp/autopkgtest-lxc.7lvlk_yq/downtmp/build.uxb/src/test/test_plugin_systemd.rb:42:in `test_systemd_notify_usr2_hot_restart_cluster' 189s /tmp/autopkgtest-lxc.7lvlk_yq/downtmp/build.uxb/src/test/helper.rb:90:in `block (4 levels) in run' 189s /usr/lib/ruby/3.1.0/timeout.rb:107:in `block in timeout' 189s /usr/lib/ruby/3.1.0/timeout.rb:117:in `timeout' 189s /tmp/autopkgtest-lxc.7lvlk_yq/downtmp/build.uxb/src/test/helper.rb:88:in `block (3 levels) in run' OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072533: procps: flaky autopkgtest:
Source: procps Version: 2:4.0.4-4 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package, because it showed up in the glibc regressions. I noticed that it regularly fails on amd64, ppc64el and s390x. For your info, as it seems to correlate, those are the architectures where multiple tests run in parallel, each in their own lxc container. 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 E.g. https://ci.debian.net/packages/p/procps/testing/amd64/47064938/ 52s autopkgtest [06:08:26]: test vmstat: [--- 53s test_no_arguments 53s [1;31mASSERT:[0mvalue line 53s [1;31mshunit2:ERROR[0m test_no_arguments() returned non-zero return code. 53s test_forks 53s test_disk 53s 53s Ran [1;36m3[0m tests. 53s 53s [1;31mFAILED[0m ([1;31mfailures=2[0m) 53s autopkgtest [06:08:27]: test vmstat: ---] OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072308: src:coq: fails to migrate to testing for too long: autopkgtest issues due to dependencies
Source: coq Version: 8.18.0+dfsg-1 Severity: serious Control: close -1 8.19.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:coq has been trying to migrate for 35 days [2]. Hence, I am filing this bug. The version in unstable is blocked by autopkgtest failures in reverse (test) dependencies on s390x, which seem to be happen due to some missing (test) dependency. 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=coq OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072307: src:nvptx-tools: fails to migrate to testing for too long: BD on llvm-toolchain-18 binaries
Source: nvptx-tools Version: 0.20230904-1 Severity: serious Control: close -1 0.20240423-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:nvptx-tools has been trying to migrate for 38 days [2]. Hence, I am filing this bug. The version in unstable Build-Depends on binaries from llvm-toolchain-18 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=nvptx-tools OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072306: src:r-cran-rcppparallel: fails to migrate to testing for too long: autopkgtest regression
Source: r-cran-rcppparallel Version: 5.1.7+dfsg-3 Severity: serious Control: close -1 5.1.7+dfsg-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:r-cran-rcppparallel has been trying to migrate for 38 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-rcppparallel OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072305: src:culmus-fancy: fails to migrate to testing for too long: uploader built arch:all binaries
Source: culmus-fancy Version: 0.0.20140315-1 Severity: serious Control: close -1 0.0.20240129 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:culmus-fancy has been trying to migrate for 41 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=culmus-fancy OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072304: src:gnome-shell-extension-appindicator: fails to migrate to testing for too long: versioned dependency not in unstable
Source: gnome-shell-extension-appindicator Version: 53-2 Severity: serious Control: close -1 58-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1071926 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-shell-extension-appindicator has been trying to migrate for 42 days [2]. Hence, I am filing this bug. The version in unstable depends on a version of gnome-shell that's not in unstable or testing, as reported in bug 1071926. 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=gnome-shell-extension-appindicator OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072303: src:libmaus2: fails to migrate to testing for too long: FTBFS on arm64
Source: libmaus2 Version: 2.0.813+ds-1 Severity: serious Control: close -1 2.0.813+ds-3 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1069691 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:libmaus2 has been trying to migrate for 44 days [2]. Hence, I am filing this bug. The version in unstable failed to build on arm64 as reported in bug 1069691. 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=libmaus2 OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072302: src:gnome-shell-mailnag: fails to migrate to testing for too long: versioned dependency not yet in unstable
Source: gnome-shell-mailnag Version: 40.0-5 Severity: serious Control: close -1 40.0-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:gnome-shell-mailnag has been trying to migrate for 46 days [2]. Hence, I am filing this bug. The version in unstable depends on a version of gnome-shell that's not even in unstable. 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=gnome-shell-mailnag OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072271: src:skimage: fails to migrate to testing for too long: FTBFS on mips64el
Source: skimage Version: 0.22.0-3 Severity: serious Control: close -1 0.23.2-1 Tags: sid trixie ftbfs 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:skimage has been trying to migrate for 49 days [2]. Hence, I am filing this bug. The version in unstable failed to build on mips64el. 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=skimage OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071147: bluez: autopkgtests fail due to lack of devices
Hi, On Wed, 15 May 2024 10:16:55 +0200 Emilio Pozuelo Monfort wrote: If this can't be fixed in the short term by adding some type of restriction to the autopkgtest or by mocking the devices, then the tests should be removed until they can be made to work on our infrastructure. The autopkgtest failure is not due to the test failing itself, but due to the test writing to stderr, which by default is considered a test failure. You can ignore output to stderr by marking the test with the allow-stderr restriction. But please, if you do that, this test doesn't actually do anything anymore on Debian infrastructure so be sure to also mark it as superficial or mark the test as skippable and exit with exit code 77 in case all tests are skipped. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072269: src:python-arrow: fails to migrate to testing for too long: uploader built arch:all binaries
Source: python-arrow Version: 1.2.3-1 Severity: serious Control: close -1 1.3.0-1 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:python-arrow has been trying to migrate for 52 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=python-arrow OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072270: src:bluez: fails to migrate to testing for too long: autopkgtest failure
Source: bluez Version: 5.71-1 Severity: serious Control: close -1 5.73-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1071147 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:bluez has been trying to migrate for 50 days [2]. Hence, I am filing this bug. The version in unstable is blocked from migration because it fails it's own autopkgtest, as reported in bug 1071147. 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=bluez OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072268: src:rake: fails to migrate to testing for too long: causes autopkgtest issues
Source: rake Version: 13.0.6-3 Severity: serious Control: close -1 13.2.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:rake has been trying to migrate for 58 days [2]. Hence, I am filing this bug. The version in unstable causes the autopkgtest of src:ruby-hoe to fail. 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=rake OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072243: src:zmat: fails to migrate to testing for too long: FTBFS on non-x86
Source: zmat Version: 0.9.8+ds-8 Severity: serious Control: close -1 0.9.9+ds.1-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1068683 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:zmat has been trying to migrate for 57 days [2]. Hence, I am filing this bug. As reported in bugs 1068683 and 10686834, the version in unstable fails to build nearly everywhere. 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=zmat OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1068349: nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean
Hi, On Sun, 19 May 2024 16:25:01 +0100 "Rebecca N. Palmer" wrote: Filing a bug against two packages means that it could be fixed in *either* of them, *not* that it requires changes to both of them. Hence, it is correct that this bug was closed. While I recall it's documented like this, this is not how the BTS reports this bug to the outside world and the migration software is still informed that this bug affects src:lxml with its version in unstable and hence blocks migration. Are you saying that if lxml migrates to testing, everything is fine? Than the easiest thing to do is to assign this bug to the package that fixed it. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072242: src:git-delta: fails to migrate to testing for too long: FTBFS on arm64, armel and ppc64el
Source: git-delta Version: 0.16.5-5 Severity: serious Control: close -1 0.17.0-1 Tags: sid trixie ftbfs 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 58 days [2]. Hence, I am filing this bug. The version in unstable failed to build on arm64, armel and ppc64el. 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=git-delta OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072241: src:manpages: fails to migrate to testing for too long: RC bug and B-D not in testing
Source: manpages Version: 6.05.01-1 Severity: serious Control: close -1 6.8-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1072158 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:manpages has been trying to migrate for 59 days [2]. Hence, I am filing this bug. The version in unstable has an unresolved RC bug (#1072158) and one of its Build-Depends isn't in testing and can't 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=manpages OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072110: glslang breaks shaderc autopkgtest: undefined reference: ABI breakage?? -- not the case
Hi. [Just in case you're not aware, the BTS doesn't forward replies to the bug submitter unless they are subscribed. If you want to have the submitters attention, please add them explicitly.] On Wed, 29 May 2024 19:55:19 +0200 Philippe SWARTVAGHER wrote: Well, this issue is "normal". Currently, shaderc 2023.2-1 is in testing. This version suffers from an "undefined symbol" bug (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070983). This bug is fixed in version 2023.8-1 which is now in unstable. Can you please elaborate how the fix works. This feels like you're using a symbol that's only available from a new version of glslang, why don't you have the right versioned constrained to prevent migration of shaderc without the right version providing the symbol? And how can the test of shaderc in testing work with the version of glslang in testing? It really looks like src:glslang is still failing to provide the symbol that shaderc (and maybe other packages in testing) are expecting from it. What I mean to say is that very regularly when an ABI breaks "just rebuilding" reverse dependencies fixes missing symbol issues, but it's the wrong fix. Bumping SONAME when ABI breaks and going through a transition is the right solution if the dropping of the symbol is intended. (I'm not saying that's the case here as I don't fully understand it). However, this version never migrated to testing due to a blocking bug in glslang (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062799). This bug in glslang is now fixed with the last upload. But the new version of glslang still doesn't provide the missing symbol. I'm a beginner regarding this kind transition / blocking bug / CI, so I don't know how this bug can be solved... From where I stand this looks like ABI is broken and if it's not going to be reverted, the SONAME must be bumped and we have to go through a transition: https://wiki.debian.org/Teams/ReleaseTeam/Transitions I don't know if it helps, but I have a RFS (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072181) for a new version of shaderc (which changes nothing about this bug). You can see on Salsa that autopkgtests pass with the version of glslang available in unstable: https://salsa.debian.org/debian/shaderc/-/pipelines/683648. Well, shaderc in unstable is build against the new version of glslang. As I mentioned before, rebuilds often paper over missing symbols problems, but is the wrong solution. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072110: glslang breaks shaderc autopkgtest: undefined reference: ABI breakage??
Source: glslang, shaderc Control: found -1 glslang/14.2.0-1 Control: found -1 shaderc/2023.2-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of glslang the autopkgtest of shaderc fails in testing when that autopkgtest is run with the binary packages of glslang from unstable. It passes when run with only packages from testing. In tabular form: passfail glslangfrom testing14.2.0-1 shadercfrom testing2023.2-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Normally "undefined reference to ..." means an ABI bump without a SONAME change. Is that the case here too? Currently this regression is blocking the migration of glslang to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=glslang https://ci.debian.net/data/autopkgtest/testing/arm64/s/shaderc/47069332/log.gz 80s /usr/bin/ld: /usr/lib/gcc/aarch64-linux-gnu/13/../../../aarch64-linux-gnu/libshaderc.so: undefined reference to `glslang::TIntermediate::improperStraddle(glslang::TType const&, int, int)' 80s collect2: error: ld returned 1 exit status 80s autopkgtest [15:07:47]: test lib OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071907: src:traitlets: fails to migrate to testing for too long: causes issues in src:jupyter-notebook
Source: traitlets Version: 5.5.0-2 Severity: serious Control: close -1 5.14.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:traitlets has been trying to migrate for 54 days [2]. Hence, I am filing this bug. The version in unstable causes autopkgtest failure in src:jupyter-notebook. 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=traitlets OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071906: src:mame: fails to migrate to testing for too long: FTBFS on armel
Source: mame Version: 0.261+dfsg.1-1 Severity: serious Control: close -1 0.264+dfsg.1-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1069544 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:mame has been trying to migrate for 57 days [2]. Hence, I am filing this bug. The version in unstable failed to build on armel as reported in bug 1069544. 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=mame OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071905: src:python-ppmd: fails to migrate to testing for too long: FTBFS on mips64el and ppc64el
Source: python-ppmd Version: 0.3.3-5 Severity: serious Control: close -1 0.5.0-1 Tags: sid trixie ftbfs 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-ppmd has been trying to migrate for 59 days [2]. Hence, I am filing this bug. The version in unstable failed to build on mips64el and ppc64el. 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-ppmd OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071856: src:alttab: fails to migrate to testing for too long: autopkgtest regression
Source: alttab Version: 1.7.1-1 Severity: serious Control: close -1 1.7.1-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:alttab has been trying to migrate for 65 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=alttab OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071857: src:python-watson-developer-cloud: fails to migrate to testing for too long: uploader built arch:all binary
Source: python-watson-developer-cloud Version: 7.0.0-1 Severity: serious Control: close -1 8.0.0-1 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:python-watson-developer-cloud has been trying to migrate for 61 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=python-watson-developer-cloud OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071854: src:matrix-synapse: fails to migrate to testing for too long: RC bug
Source: matrix-synapse Version: 1.100.0-1 Severity: serious Control: close -1 1.103.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1069763 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:matrix-synapse has been trying to migrate for 66 days [2]. Hence, I am filing this bug. The version in unstable doesn't migrate because bug 1069763 is filed against that version, although I somehow assume it applies equally against the version in testing. 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=matrix-synapse OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071853: src:postsrsd: fails to migrate to testing for too long: FTBFS on armel and armhf
Source: postsrsd Version: 1.10-2 Severity: serious Control: close -1 1.10-2.1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1068053 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:postsrsd has been trying to migrate for 66 days [2]. Hence, I am filing this bug. The version in unstable fails to build on armel and armhf as reported in bug 1068053. 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=postsrsd OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071852: src:python-uinput: fails to migrate to testing for too long: FTBFS on armel and armhf
Source: python-uinput Version: 0.11.3-1 Severity: serious Control: close -1 1.0.1-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1067083 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-uinput has been trying to migrate for 68 days [2]. Hence, I am filing this bug. The version in unstable failed to build on armel and armhf as reported in bug 1067083. 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-uinput OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071851: src:remmina: fails to migrate to testing for too long: unresolved RC bug
Source: remmina Version: 1.4.34+dfsg-1 Severity: serious Control: close -1 1.4.35+dfsg-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1070063 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:remmina has been trying to migrate for 70 days [2]. Hence, I am filing this bug. The version in unstable has an unresolved RC bug: 1070063. 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=remmina OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071850: src:python-dmidecode: fails to migrate to testing for too long: new autopkgtest fails everywhere
Source: python-dmidecode Version: 3.12.3-2 Severity: serious Control: close -1 3.12.3-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:python-dmidecode has been trying to migrate for 72 days [2]. Hence, I am filing this bug. The version in unstable has a newly added autopkgtest (thanks for that), but it fails everywhere. 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-dmidecode OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071849: src:creduce: fails to migrate to testing for too long: blocked by Build-Depends
Source: creduce Version: 2.11.0~20231125-2 Severity: serious Control: close -1 2.11.0~20240312-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:creduce has been trying to migrate for 74 days [2]. Hence, I am filing this bug. The version in unstable Build-Depends on src:llvm-toolchain-18 which isn't ready to migrate to testing 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=creduce OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071846: src:cvise: fails to migrate to testing for too long: blocked by Build-Depends
Source: cvise Version: 2.9.0-2 Severity: serious Control: close -1 2.10.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:cvise has been trying to migrate for 74 days [2]. Hence, I am filing this bug. The version in unstable build depends on src:llvm-toolchain-18 which isn't ready to migrate to testing 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=cvise OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071844: src:libfiu: fails to migrate to testing for too long: FTBFS on armel and armhf
Source: libfiu Version: 1.2-1 Severity: serious Control: close -1 1.2-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1066938 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:libfiu has been trying to migrate for 75 days [2]. Hence, I am filing this bug. The version in unstable failed to build on armel and armhf as reported in bug 1066938. 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=libfiu OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071843: src:r-cran-pracma: fails to migrate to testing for too long: uploader built arch:all binary
Source: r-cran-pracma Version: 2.4.4-1 Severity: serious Control: close -1 2.4.4-2 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:r-cran-pracma has been trying to migrate for 75 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=r-cran-pracma OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071842: src:rust-gsettings-macro: fails to migrate to testing for too long: Build-Depends not available
Source: rust-gsettings-macro Version: 0.1.20-1 Severity: serious Control: close -1 0.2.0-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1068142 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-gsettings-macro has been trying to migrate for 76 days [2]. Hence, I am filing this bug. The version in unstable fails to build due to missing Build-Depends as reported in bug 1068142. 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-gsettings-macro OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071782: skimage: autopkgtest needs update for new version of pytest on s390x
Source: skimage
Version: 0.22.0-3
Severity: serious
X-Debbugs-CC: pyt...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pytest
Dear maintainer(s),
With a recent upload of pytest the autopkgtest of skimage fails in
testing on s390x when that autopkgtest is run with the binary packages
of pytest from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
pytest from testing8.1.2-1
skimagefrom testing0.22.0-3
all others from testingfrom testing
I copied some of the output at the bottom of this report. I'll note that
s390x is our only big endian architecture with autopgktest.
Currently this regression is blocking the migration of pytest to testing
[1]. Of course, pytest shouldn't just break your autopkgtest (or even
worse, your package), but due to the nature of the package pytest I
suspect that your package just needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from pytest should really add
a versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=pytest
https://ci.debian.net/data/autopkgtest/testing/s390x/s/skimage/46978110/log.gz
=== FAILURES
===
300s __ test_imread_handle
__
300s 300s def test_imread_handle():
300s expected = np.load(fetch('data/chessboard_GRAY_U8.npy'))
300s with open(fetch('data/chessboard_GRAY_U16.tif'), 'rb') as fh:
300s img = imread(fh)
300s > assert img.dtype == np.uint16
300s E AssertionError: assert dtype('
300s E+ where dtype('0, 0],\n [255, 255, 255, ..., 0, 0, 0],\n [255, 255,
255, ..., 0, 0, 0],\n ...,\n [ 0, 0, 0, ..., 255,
255, 255],\n [ 0, 0, 0, ..., 255, 255, 255],\n [ 0,
0, 0, ..., 255, 255, 255]], dtype='
300s E+ and= np.uint16
300s 300s
/usr/lib/python3/dist-packages/skimage/io/tests/test_tifffile.py:48:
AssertionError
300s === warnings summary
===
300s filters/tests/test_unsharp_mask.py: 480 warnings
300s
/usr/lib/python3/dist-packages/skimage/filters/tests/test_unsharp_mask.py:26:
RuntimeWarning: invalid value encountered in cast
300s array = ((array + offset) * 128).astype(dtype)
300s 300s io/tests/test_pil.py::test_png_round_trip
300s io/tests/test_pil.py::test_imsave_filelike
300s
/usr/lib/python3/dist-packages/skimage/io/_plugins/pil_plugin.py:105:
DeprecationWarning: The binary mode of fromstring is deprecated, as it
behaves surprisingly on unicode inputs. Use frombuffer instead
300s frame = np.fromstring(frame.tobytes(), dtype)
300s 300s measure/tests/test_fit.py::test_ellipse_parameter_stability
300s /usr/lib/python3/dist-packages/skimage/measure/fit.py:526:
RuntimeWarning: divide by zero encountered in scalar divide
300s phi = 0.5 * np.arctan((2. * b) / (a - c))
300s 300s
transform/tests/test_pyramids.py::test_pyramid_dtype_support[pyramid_gaussian-uint8]
300s
transform/tests/test_pyramids.py::test_pyramid_dtype_support[pyramid_laplacian-uint8]
300s
/usr/lib/python3/dist-packages/skimage/transform/tests/test_pyramids.py:208:
RuntimeWarning: invalid value encountered in cast
300s img = np.random.randn(32, 8).astype(dtype)
300s 300s
../../../../usr/lib/python3/dist-packages/_pytest/cacheprovider.py:446
300s /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:446:
PytestCacheWarning: could not create cache path
/usr/lib/python3/dist-packages/skimage/.pytest_cache/v/cache/nodeids:
[Errno 13] Permission denied:
'/usr/lib/python3/dist-packages/skimage/.pytest_cache'
300s config.cache.set("cache/nodeids", sorted(self.cached_nodeids))
300s 300s
../../../../usr/lib/python3/dist-packages/_pytest/cacheprovider.py:398
300s /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:398:
PytestCacheWarning: could not create cache path
/usr/lib/python3/dist-packages/skimage/.pytest_cache/v/cache/lastfailed:
[Errno 13] Permission denied:
'/usr/lib/python3/dist-packages/skimage/.pytest_cache'
300s config.cache.set("cache/lastfailed", self.lastfailed)
300s 300s ../../../../usr/lib/python3/dist-packages/_pytest/stepwise.py:57
300s /usr/lib/python3/dist-packages/_pytest/stepwise.py:57:
PytestCacheWarning: could not create cache path
Bug#1071767: fpdf2: autopkgtest needs update for new version of pytest
Source: fpdf2
Version: 2.7.9-1
Severity: serious
X-Debbugs-CC: pyt...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pytest
Dear maintainer(s),
With a recent upload of pytest the autopkgtest of fpdf2 fails in testing
when that autopkgtest is run with the binary packages of pytest from
unstable. It passes when run with only packages from testing. In tabular
form:
passfail
pytest from testing8.1.2-1
fpdf2 from testing2.7.9-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of pytest to testing
[1]. Of course, pytest shouldn't just break your autopkgtest (or even
worse, your package), but given the nature of the package pytest, I
suspect your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from pytest should really add
a versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=pytest
https://ci.debian.net/data/autopkgtest/testing/amd64/f/fpdf2/46966995/log.gz
=== FAILURES
===
263s __ test_multi_cell_split_only
__
263s 263s def test_multi_cell_split_only(): # discussion 314
263s pdf = FPDF()
263s pdf.add_page()
263s pdf.set_font("Helvetica", size=TEXT_SIZE)
263s text = "Lorem ipsum Ut nostrud irure reprehenderit anim
nostrud dolore sed ut"
263s expected = [
263s "Lorem ipsum Ut nostrud irure",
263s "reprehenderit anim nostrud",
263s "dolore sed ut",
263s ]
263s with pytest.warns(
263s DeprecationWarning, match='The parameter "split_only"
is deprecated.'
263s ) as record:
263s assert (
263s pdf.multi_cell(w=0, h=LINE_HEIGHT, text=text,
split_only=True) == expected
263s )
263s > assert len(record) == 1
263s E assert 2 == 1
263s E+ where 2 = len(WarningsChecker(record=True))
263s 263s test/text/test_multi_cell.py:267: AssertionError
263s === warnings summary
===
263s test/image/test_vector_image.py::test_svg_image_no_viewbox
263s
/tmp/autopkgtest-lxc.vf1cnias/downtmp/build.w5B/src/test/image/test_vector_image.py:45:
UserWarning: has no "viewBox", using its "width" & "height" as
default "viewBox"
263s img = pdf.image(SVG_SRCDIR / "simple_rect_no_viewbox.svg")
263s 263s
test/image/test_vector_image.py::test_svg_image_with_custom_width_and_no_viewbox
263s
/tmp/autopkgtest-lxc.vf1cnias/downtmp/build.w5B/src/test/image/test_vector_image.py:75:
UserWarning: has no "viewBox", using its "width" & "height" as
default "viewBox"
263s img = pdf.image(SVG_SRCDIR / "simple_rect_no_viewbox.svg", w=60)
263s 263s
test/image/test_vector_image.py::test_svg_image_with_custom_size_and_no_viewbox
263s
/tmp/autopkgtest-lxc.vf1cnias/downtmp/build.w5B/src/test/image/test_vector_image.py:106:
UserWarning: has no "viewBox", using its "width" & "height" as
default "viewBox"
263s img = pdf.image(SVG_SRCDIR / "simple_rect_no_viewbox.svg",
x=50, y=50, w=30, h=60)
263s 263s
test/image/test_vector_image.py::test_svg_image_style_inherited_from_fpdf
263s
/tmp/autopkgtest-lxc.vf1cnias/downtmp/build.w5B/src/test/image/test_vector_image.py:132:
UserWarning: has no "viewBox", using its "width" & "height" as
default "viewBox"
263s pdf.image(
263s 263s test/image/test_vector_image.py::test_svg_image_from_bytesio
263s
/tmp/autopkgtest-lxc.vf1cnias/downtmp/build.w5B/src/test/image/test_vector_image.py:145:
UserWarning: has no "viewBox", using its "width" & "height" as
default "viewBox"
263s pdf.image(
263s 263s test/image/test_vector_image.py::test_svg_image_from_bytes
263s
/tmp/autopkgtest-lxc.vf1cnias/downtmp/build.w5B/src/test/image/test_vector_image.py:158:
UserWarning: has no "viewBox", using its "width" & "height" as
default "viewBox"
263s pdf.image(
263s 263s
test/table/test_table_extraction.py::test_camelot_extract_simple_table[table_simple.pdf-lattice]
263s
test/table/test_table_extraction.py::test_camelot_extract_simple_table[table_with_images.pdf-lattice]
263s
test/table/test_table_extraction.py::test_camelot_extract_simple_table[table_with_images_and_img_fill_width.pdf-lattice]
263s
Bug#1071766: src:sccache: fails to migrate to testing for too long: FTBFS
Source: sccache Version: 0.7.7-1 Severity: serious Control: close -1 0.8.0-3 Tags: sid trixie ftbfs 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:sccache has been trying to migrate for 81 days [2]. Hence, I am filing this bug. The version in unstable failed to build. 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=sccache OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071764: src:kmod: fails to migrate to testing for too long: unresolved RC bug
Source: kmod Version: 31+20240202-2 Severity: serious Control: close -1 32-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:kmod has been trying to migrate for 76 days [2]. Hence, I am filing this bug. The version in unstable has an unresolved RC bug (it failed to build on buildds for armel and armhf). 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=kmod OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071413: src:rust-debversion: fails to migrate to testing for too long: RC buggy Depends
Source: rust-debversion Version: 0.2.2-1 Severity: serious Control: close -1 0.3.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-debversion has been trying to migrate for 70 days [2]. Hence, I am filing this bug. The version in unstable apparently has a new dependency chain that ends with rust-rsa which has an unresolved RC security issue and isn't migrating to testing. 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-debversion OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071412: src:tracker: fails to migrate to testing for too long: autopkgtest regression
Source: tracker Version: 3.4.2-3 Severity: serious Control: close -1 3.7.3-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1068468 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:tracker has been trying to migrate for 71 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest as reported in bug 1068468. 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=tracker OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071410: src:diffoscope: fails to migrate to testing for too long: FTBFS and blocked by Build-Depends
Source: diffoscope Version: 259 Severity: serious Control: close -1 267 Tags: sid trixie ftbfs 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:diffoscope has been trying to migrate for 71 days [2]. Hence, I am filing this bug. The version in unstable failed to build and is also blocked by apktool, which was removed from testing due to an unresolved RC 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. 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=diffoscope OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071409: src:fakeroot: fails to migrate to testing for too long: FTBFS on armel, armhf
Source: fakeroot Version: 1.33-1 Severity: serious Control: close -1 1.34-1 Tags: sid trixie ftbfs 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:fakeroot has been trying to migrate for 73 days [2]. Hence, I am filing this bug. The version in unstable failed to build on armel and armhf. On reproducible-builds, a build on i386, arm64 and armhf today also failed (only amd64 passed). 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=fakeroot OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071403: src:geoalchemy2: fails to migrate to testing for too long: B-D on mysql which isn't allowed to migrate
Source: geoalchemy2 Version: 0.13.3-2 Severity: serious Control: close -1 0.14.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:geoalchemy2 has been trying to migrate for 73 days [2]. Hence, I am filing this bug. The version in unstable build depends on mysql, which for security support isn't allowed to migrate (Debian has MariaDB). 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=geoalchemy2 OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071402: src:gnome-shell-extension-arc-menu: fails to migrate to testing for too long: unsatisfiable dependency
Source: gnome-shell-extension-arc-menu Version: 49+forkv29-4 Severity: serious Control: close -1 55-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-shell-extension-arc-menu has been trying to migrate for 75 days [2]. Hence, I am filing this bug. The version in unstable has unsatisfiable dependencies. 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=gnome-shell-extension-arc-menu OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071401: src:cross-toolchain-base-mipsen: unsatisfied build dependency in testing: linux-source-6.6 (>= 6.6.11)
Source: cross-toolchain-base-mipsen Version: 27 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#1071399: src:ndcube: unsatisfied build dependency in testing: python3-sunpy
Source: ndcube Version: 2.2.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#1071400: src:specutils: unsatisfied build dependency in testing: python3-spectral-cube
Source: specutils Version: 1.14.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#1071398: src:tea-cli: unsatisfied build dependency in testing: golang-github-go-git-go-git-dev
Source: tea-cli Version: 0.9.2-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#1071397: src:ngspetsc: unsatisfied build dependency in testing: fenicsx
Source: ngspetsc Version: 0.0~git20240318.f83b50a-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#1057282: linux-image-6.5.0-0.deb12.1-arm64: arm64 kernel upgrade makes systems unresponsive
Hi Ben (and all the rest), On 15-05-2024 9:56 p.m., Ben Hutchings wrote: Apologies for leaving this bug for so long. NP, part of live I guess. Is this bug still occurring? I don't know. The problem was severe enough for us to abandon the idea of running the backport kernels on our arm64 hosts, so we went back to the stable kernel there. I had a look for possibly related fixes, and found: commit 22e111ed6c83dcde3037fc81176012721bc34c0b [...] The fix went into 6.8-rc1 and was backported to 6.6.15, so Debian versions 6.6.15-1 onward should have it. commit a8b0026847b8c43445c921ad2c85521c92eb175f [...] which went into 6.8 but was *not* backported. If you think it worth enough knowing if either is the case, I can install the backports kernel again on the arm64 hosts, but obviously that will be annoying for us. Please let me know if I should pursue this (I would be expecting a bit quicker turn around on this bug if you say yes now ;) ). If the bug is still occurring, can you say what type of filesystem rsync is being run on? I'm not sure if this is the answer you're looking for, we use ext4. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071070: src:nbd: fails to migrate to testing for too long: autopkgtest failure
Source: nbd Version: 1:3.25-1 Severity: serious Control: close -1 1:3.26.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:nbd has been trying to migrate for 71 days [2]. Hence, I am filing this bug. You added an autopkgtest to your package (thank you for that), but it fails. This is blocking 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=nbd OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1069447: gpaw: FTBFS on armhf: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" --test-pytest "--test-args=-v -m ci" returned exit code 13
Control: tags -1 moreinfo Hi Lucas, [Please CC me on replies, I'm not subscribed to the bug] On Sat, 20 Apr 2024 15:09:56 +0200 Lucas Nussbaum wrote: During a rebuild of all packages in sid, your package failed to build on armhf. Do you have any idea why we don't see the same failure on reproducible-builds [1]? Paul [1] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gpaw.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071069: src:prettytable: fails to migrate to testing for too long: FTBFS
Source: prettytable Version: 3.6.0-1 Severity: serious Control: close -1 3.6.0-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1066757 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:prettytable has been trying to migrate for 72 days [2]. Hence, I am filing this bug. The version in unstable failed to build as reported in bug 1066757. 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=prettytable OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071067: src:sqlmodel: fails to migrate to testing for too long: FTBFS
Source: sqlmodel Version: 0.0.8-5 Severity: serious Control: close -1 0.0.8-6 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1066771 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:sqlmodel has been trying to migrate for 72 days [2]. Hence, I am filing this bug. The version in unstable failed to build as reported in bug 1066771. 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=sqlmodel OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071003: src:audit: fails to migrate to testing for too long: piuparts regression
Source: audit Version: 1:3.1.2-2 Severity: serious Control: close -1 1:3.1.2-2.1 X-Debbugs-CC: vor...@debian.org Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1070327 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 74 days [2]. Hence, I am filing this bug. The version in unstable has postrm issues as reported in 1070327. 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=audit OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070995: src:eclib: fails to migrate to testing for too long: FTBFS on arm 32 bits
Source: eclib Version: 20231212-1 Severity: serious Control: close -1 20240408-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1069515 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:eclib has been trying to migrate for 74 days [2]. Hence, I am filing this bug. The version in unstable failed to build on armel and armhf, as reported in bug 106.9515 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=eclib OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070994: src:praat: fails to migrate to testing for too long: FTBFS on arm64, armel, armhf, ppc64el and riscv64
Source: praat Version: 6.4.05+dfsg-1 Severity: serious Tags: sid trixie ftbfs 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:praat has been trying to migrate for 74 days [2]. Hence, I am filing this bug. The version in unstabled failed to build on most architectures where it build before. 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=praat OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070993: src:ukui-power-manager: fails to migrate to testing for too long: unresolved RC bug
Source: ukui-power-manager Version: 3.1.1-1 Severity: serious Control: close -1 4.0.0.1-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1070426 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:ukui-power-manager has been trying to migrate for 77 days [2]. Hence, I am filing this bug. The version in unstable is blocked by bug 1070426. 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=ukui-power-manager OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070989: src:ruby-parslet: fails to migrate to testing for too long: triggers autopkgtest issues
Source: ruby-parslet Version: 1.8.2-4 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:ruby-parslet has been trying to migrate for 79 days [2]. Hence, I am filing this bug. The version in unstable causes autopkgtest issues in src:ruby-toml (although from the log it's not clear why as all tests seem to pass but still exit code is 1). 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-parslet OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070988: src:q2-feature-table: fails to migrate to testing for too long: autopkgtest regression
Source: q2-feature-table Version: 2023.9.0+dfsg-1 Severity: serious Control: close -1 2024.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:q2-feature-table has been trying to migrate for 84 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=q2-feature-table OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070987: src:tiktoken: fails to migrate to testing for too long: autopkgtest regression
Source: tiktoken Version: 0.4.0-2 Severity: serious Control: close -1 0.6.0-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:tiktoken has been trying to migrate for 84 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=tiktoken OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070982: src:click: fails to migrate to testing for too long: autopkgtest regression on !amd64
Source: click Version: 0.5.0-10 Severity: serious Control: close -1 0.5.2-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:click has been trying to migrate for 60 days [2]. Hence, I am filing this bug. The autopkgtest of the version in unstable fails everywhere 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=click OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1068363: src:autopkgtest: flaky autopkgtest (host dependent?) on ppc64el
Control: tags -1 pending Hi, On 06-04-2024 9:58 p.m., Paul Gevers wrote: Anyways, it looks like we could just lower the timeout to 1 second and hope were fine for some time to come. No. 1 second is *too short* for the PodmanRunner.test_copy_timeout test on salsa. So I'll just disable the test for now. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070818: src:libcbor: fails to migrate to testing for too long: FTBFS on mips64el
Source: libcbor Version: 0.10.2-1.1 Severity: serious Control: close -1 0.10.2-1.2 Tags: sid trixie ftbfs 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:libcbor has been trying to migrate for 83 days [2]. Hence, I am filing this bug. The version in unstable failed to build from source on mips64el. 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=libcbor OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070816: src:wsdd: fails to migrate to testing for too long: uploader built arch:all binaries
Source: wsdd Version: 2:0.7.0-2.1 Severity: serious Control: close -1 2:0.7.1-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:wsdd has been trying to migrate for 82 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=wsdd OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070814: src:snapraid: fails to migrate to testing for too long: FTBFS on mips64el
Source: snapraid Version: 12.2-1 Severity: serious Control: close -1 12.3-1 Tags: sid trixie ftbfs 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:snapraid has been trying to migrate for 84 days [2]. Hence, I am filing this bug. The version in unstable failed to build on mips64el. 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=snapraid OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070813: src:camelot-py: fails to migrate to testing for too long: autopkgtest failure on ppc64el
Source: camelot-py
Version: 0.11.0-3
Severity: serious
Control: close -1 0.11.0-4
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1063891
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:camelot-py has been trying to migrate for
86 days [2]. Hence, I am filing this bug. As you noticed yourself (in
bug 1063891) the autopkgtest fails on ppc64el. If you can't easily fix
it, I suggest you make the test failure on ppc64el not blocking. You can
do that by either using the Architecture field in d/t/control
("!ppc64el" works), but I don't recommend that because changes to the
results would go unnoticed and it would be harder to get a log.
Alternatively you can annotate the test with the flaky restriction, but
that would cause failure on !ppc64el to go unnoticed. So, I would
recommend using the skippable restriction and "exit 77" when the test
fails on ppc64el (but that's a bit more work to embed in the test).
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=camelot-py
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1070810: src:unattended-upgrades: fails to migrate to testing for too long: FTBFS
Source: unattended-upgrades Version: 2.9.1+nmu4 Severity: serious Control: close -1 2.10 Tags: sid trixie ftbfs 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:unattended-upgrades has been trying to migrate for 87 days [2]. Hence, I am filing this bug. The version in unstable failed to build. 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=unattended-upgrades OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070809: src:multiqc: fails to migrate to testing for too long: depends on package that doesn't migrate
Source: multiqc Version: 1.14+dfsg-1.1 Severity: serious Control: close -1 1.18+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:multiqc has been trying to migrate for 87 days [2]. Hence, I am filing this bug. The version in unstable has a new (Build-)Depends that's not ready to migrate yet (it needs a source-full upload). 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=multiqc OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070706: gtk4 udeb has unsatisfiable dependencies
Hi, On 07-05-2024 7:49 p.m., Simon McVittie wrote: The version in testing, 4.12.5+ds-3, has the same dependencies, so this is not a regression. Is it? It seems that the version in unstable depends on libpng16-16t64-udeb where the version in testing depends on libpng16-16-udeb. The later exists, the former not. Is this requirement newly enforced by britney? No. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070401: sqlite3 breaks tracker autopkgtest: killed by signal 6 SIGABRT
Control: reassign -1 src:tracker Control: found -1 3.4.2-3 Control: affects -1 src:sqlite3 Hi László, On 05-05-2024 11:24 a.m., László Böszörményi (GCS) wrote: It's the tracker autopkg testing that needs fixing. So, I'm inclined to agree with your assessment, so let's reassign this to src:tracker. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070422: src:intel-vc-intrinsics: unsatisfied build dependency in testing: llvm-14-dev
Source: intel-vc-intrinsics Version: 0.18.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. We have several version of src:llvm-toolchain-* in Debian, 14 is not going to come back into testing as it's too old. You'll have to use a newer version, ideally using the non-versioned default flavor: llvm-dev. 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#1070421: src:mac-widgets: unsatisfied build dependency in testing: libjgoodies-forms-java-doc
Source: mac-widgets Version: 0.10.0+svn416-dfsg1-3 Severity: serious Tags: sid trixie ftbfs 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. src:libjgoodies-forms-java stopped building libjgoodies-forms-java-doc in it's latest upload, so your package can no longer be build in unstable either. 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#1070420: src:vagrant: unsatisfied build dependency in testing: ruby-net-ftp (>= 0.2) | ruby-net-ftp (>= 0.2)
Source: vagrant Version: 2.3.6+dfsg-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. ruby3.2 which provides these versions of ruby-net-ftp is currently blocked by three RC bugs. I also note that the runtime dependency of bin:vagrant is non-versioned. 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#1070419: src:gnome-snapshot: unsatisfied build dependency in testing: librust-gst-plugin-gtk4-0.11-dev
Source: gnome-snapshot Version: 46~beta-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. It also currently prevents the migration of the version in unstable. 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#1070418: rapiddisk: autopkgtest regression: Bad return status for module build on kernel: 6.7.12-rt-amd64 (x86_64)
Source: rapiddisk Version: 9.1.0-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it recently started failing in unstable and testing. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/packages/r/rapiddisk/unstable/amd64/46311856/ 134s Failed command: 134s make -j64 KERNELRELEASE=6.7.12-rt-amd64 -C /lib/modules/6.7.12-rt-amd64/build M=/var/lib/dkms/rapiddisk-dkms/9.1.0/build 134s Error! Bad return status for module build on kernel: 6.7.12-rt-amd64 (x86_64) 134s Consult /var/lib/dkms/rapiddisk-dkms/9.1.0/build/make.log for more information. 134s E: rapiddisk-dkms/9.1.0 failed to build for 6.7.12-rt-amd64 134s == /var/lib/dkms/rapiddisk-dkms/9.1.0/build/make.log == 134s DKMS make.log for rapiddisk-dkms-9.1.0 for kernel 6.7.12-rt-amd64 (x86_64) 134s Sun May 5 07:20:50 UTC 2024 134s make: Entering directory '/usr/src/linux-headers-6.7.12-rt-amd64' 134s CC [M] /var/lib/dkms/rapiddisk-dkms/9.1.0/build/rapiddisk.o 134s CC [M] /var/lib/dkms/rapiddisk-dkms/9.1.0/build/rapiddisk-cache.o 134s /var/lib/dkms/rapiddisk-dkms/9.1.0/build/rapiddisk-cache.c: In function ‘dm_io_async_bvec’: 134s /var/lib/dkms/rapiddisk-dkms/9.1.0/build/rapiddisk-cache.c:198:16: error: too few arguments to function ‘dm_io’ 134s 198 | return dm_io(, num_regions, where, NULL); 134s |^ 134s In file included from /var/lib/dkms/rapiddisk-dkms/9.1.0/build/rapiddisk-cache.c:46: 134s /usr/src/linux-headers-6.7.12-common-rt/include/linux/dm-io.h:82:5: note: declared here 134s82 | int dm_io(struct dm_io_request *io_req, unsigned int num_regions, 134s | ^ 134s /var/lib/dkms/rapiddisk-dkms/9.1.0/build/rapiddisk-cache.c:199:1: error: control reaches end of non-void function [-Werror=return-type] 134s 199 | } 134s | ^ 134s cc1: some warnings being treated as errors 134s make[2]: *** [/usr/src/linux-headers-6.7.12-common-rt/scripts/Makefile.build:248: /var/lib/dkms/rapiddisk-dkms/9.1.0/build/rapiddisk-cache.o] Error 1 134s make[2]: *** Waiting for unfinished jobs 134s make[1]: *** [/usr/src/linux-headers-6.7.12-common-rt/Makefile:1936: /var/lib/dkms/rapiddisk-dkms/9.1.0/build] Error 2 134s make: *** [/usr/src/linux-headers-6.7.12-common-rt/Makefile:246: __sub-make] Error 2 134s make: Leaving directory '/usr/src/linux-headers-6.7.12-rt-amd64' OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070416: src:diffoscope: unsatisfied build dependency in testing: aapt
Source: diffoscope Version: 259 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#1035474: src:libdmx Bug#1035474: Don't include in Bookworm?
clone 1035474 -1 block 1035474 by -1 reassign -1 xorg-dev retitle -1 xorg-dev: drop dependency on libdmx-dev found -1 1:7.7+23 thanks On Wed, 31 May 2023 08:50:16 +0200 Moritz Muehlenhoff wrote: On Wed, May 31, 2023 at 09:28:02AM +0300, Timo Aaltonen wrote: > Moritz Muehlenhoff kirjoitti 3.5.2023 klo 20.44: > > Source: libdmx > > Version: 1:1.1.4-2 > > Severity: serious > > > > The Xorg folks mentioned at https://www.openwall.com/lists/oss-security/2023/05/02/3: > > > > | We have also announced that we plan to retire the following packages soon > > | and while their gitlab repos are not yet archived, we expect they will be > > | archived in the future, and encourage distros that still ship them to > > | consider retiring them on your side as well: > > | > > | lib/libdmx: > > | The Xdmx server was removed from the xorg-server sources in > > | xorg-server 21 (released Oct. 2021), so this is only useful > > | for communicating with Xdmx from the 1.20 and older releases. > > > > Given that Bookworm has xorg-server 21 and there are no rdeps in the archive, > > let's exclude it from bookworm (and remove entirely eventually)? > > sounds good Unfortunately I missed that xorg-dev depends on libdmx-dev, so this will have to wait until after the Bookworm release. Let's make a bug for xorg-dev then. I'm *assuming* it's no longer needed. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1016957: kbd-chooser: please add support for riscv64
Hi Bastian, On Sat, 9 Sep 2023 19:03:07 +0200 Bastian Germann wrote: Control: severity -1 serious Can you please elaborate? I'm not seeing anything serious in this bug report. On Wed, 10 Aug 2022 21:42:34 +0200 Holger Wansing wrote: > kbd-chooser is no longer in use, I think. > Or am I missing something? I am raising severity to serious then so that it can be autoremoved from testing. This package is a key package (because of debian-installer), so it can't be autoremoved. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1069871: netplan.io: flaky autopkgtest on s390x: eth42 interface already exists
Source: netplan.io
Version: 0.107.1-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 on s390x (and maybe on armel/armhf, but that's
hard to tell because of the time_t fall-out).
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
e.g.
https://ci.debian.net/packages/n/netplan.io/testing/s390x/45071647/
272s ==
272s ERROR: test_rename_interfaces
(__main__.TestNetworkd.test_rename_interfaces)
272s --
272s Traceback (most recent call last):
272s File
"/tmp/autopkgtest-lxc.ndthudlr/downtmp/build.hjS/src/tests/integration/base.py",
line 177, in setUp
272s self.create_devices()
272s File
"/tmp/autopkgtest-lxc.ndthudlr/downtmp/build.hjS/src/tests/integration/base.py",
line 120, in create_devices
272s raise SystemError('eth42 interface already exists')
272s SystemError: eth42 interface already exists
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1069724: slurm-wlm: autopkgtest regression on !amd64: trying to overwrite '/usr/lib/-linux-gnu/slurm-wlm/accounting_storage_mysql.so'
Source: slurm-wlm Version: 23.11.4-1.4 X-Debbugs-CC: bdr...@debian.org, vor...@debian.org, mckins...@debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of slurm-wlm the autopkgtest of slurm-wlm fails in testing when that autopkgtest is run with the binary packages of slurm-wlm from unstable. It passes when run with only packages from testing. In tabular form: passfail slurm-wlm from testing23.11.4-1.4 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=3Dslurm-wlm https://ci.debian.net/data/autopkgtest/testing/arm64/s/slurm-wlm/45786802/log.gz 96s Unpacking slurm-wlm-mysql-plugin (23.11.4-1.4) ... 96s dpkg: error processing archive /tmp/apt-dpkg-install-zn5wp3/17-slurm-wlm-mysql-plugin_23.11.4-1.4_arm64.deb (--unpack): 96s trying to overwrite '/usr/lib/aarch64-linux-gnu/slurm-wlm/accounting_storage_mysql.so', which is also in package slurm-wlm-basic-plugins 23.11.4-1.4 OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1069603: [Pkg-openssl-devel] Bug#1069603: openssl breaks libcrypt-smime-perl autopkgtest: Crypt::SMIME#setPublicKeyStore: failed to store the public cert
Hi On 21-04-2024 5:56 p.m., Sebastian Andrzej Siewior wrote: The problem is that libcrypt-smime-perl < 0.29 fails with openssl >= 3.2.0. This was solved by the Perl team with their 0.29 upload. This and 0.30 didn't migrate to testing and in the meantime we got OpenSSL into unstable which relies on that fix. The migration was delayed by the time_t transition. Ack. I figured that out too. Could britney be hinted to migrate both at the same time? This should solve the issue you pointed out. There is no "please test together" knob if that's what you mean (is that what you mean?). I have triggered the test manually, so for now the lights are green. Because those expire, I have added a hint to ignore the failure of the old version in testing. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1069603: openssl breaks libcrypt-smime-perl autopkgtest: Crypt::SMIME#setPublicKeyStore: failed to store the public cert
Source: openssl, libcrypt-smime-perl Control: found -1 openssl/3.2.1-3 Control: found -1 libcrypt-smime-perl/0.28-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of openssl the autopkgtest of libcrypt-smime-perl fails in testing when that autopkgtest is run with the binary packages of openssl from unstable. It passes when run with only packages from testing. In tabular form: passfail opensslfrom testing3.2.1-3 libcrypt-smime-perlfrom testing0.28-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of openssl to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=3Dopenssl https://ci.debian.net/data/autopkgtest/testing/amd64/libc/libcrypt-smime-perl/45599656/log.gz 50s not ok 14 - Load the default public key store 50s=20 50s # Failed test 'Load the default public key store' 50s # at t/04-taint.t line 257. 50s # died: Crypt::SMIME#setPublicKeyStore: failed to store the public cert at t/04-taint.t line 257. 50s Failed 2/7 subtests=20 OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1069554: [Pkg-pascal-devel] Bug#1069554: winff: FTBFS on armel: build-dependency not installable: libreoffice-draw-nogui
Hi, On 20-04-2024 3:22 p.m., Lucas Nussbaum wrote: The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: libreoffice-draw-nogui but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. I recall rene mentioning that parts of lo are expected to not work on armel due to java being broken. Probably the best way forward is to request binary removal on armel. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1068942: src:oscar4: unsatisfied build dependency in testing: emboss-data
Source: oscar4 Version: 5.2.0+dfsg-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#1068941: src:mdevctl: unsatisfied build dependency in testing: librust-env-logger-0.10.0+default-dev
Source: mdevctl Version: 1.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#1067067: ruby-rdiscount: FTBFS: rdiscount.c:50:17: error: implicit declaration of function ‘rb_rdiscount__get_flags’ [-Werror=implicit-function-declaration]
Hi, On Sun, 17 Mar 2024 23:37:03 +0100 Sebastian Ramacher wrote: Justification: fails to build from source (but built successfully in the past) This package is a key package (hence we can't trivially remove it from testing) and the failure is blocking the time_t transition. Can this please be looked into ASAP? Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1068589: gem2deb: autopkgtest needs update for new version of ruby3.1: "libc6 (>= 2.2.5)", "libruby3.1t64 (>= 3.1.0~preview1)", "ruby | ruby-interpreter\n"] expected to include 'ruby (>= something
Source: gem2deb Version: 2.2.2 Severity: serious X-Debbugs-CC: ruby...@packages.debian.org Tags: sid trixie User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ruby3.1 Dear maintainer(s), With a recent upload of ruby3.1 (in the time_t transition) the autopkgtest of gem2deb fails in testing when that autopkgtest is run with the binary packages of ruby3.1 from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby3.1from testing3.1.2-8.3 gem2debfrom testing2.2.2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of ruby3.1 to testing [1]. Of course, ruby3.1 shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in ruby3.1 was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from ruby3.1 should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ruby3.1 https://ci.debian.net/data/autopkgtest/testing/amd64/g/gem2deb/44893387/log.gz 42s W: Inconsistent version numbers: lib/gem2deb/version.rb says 2.1, debian/changelog says 2.2.2 42s => Unit tests ... 108s test: multibinary source package should inject dependency on ruby (>= something). : F 108s === 108s Failure: test: multibinary source package should inject dependency on ruby (>= something). (Gem2DebTest): 108s ["libc6 (>= 2.2.5)", "libruby3.1t64 (>= 3.1.0~preview1)", "ruby | ruby-interpreter\n"] expected to include 'ruby (>= something)'. 108sis not true. 108s /tmp/autopkgtest-lxc.f1vq6prr/downtmp/build.NZh/src/test/integration/gem2deb_test.rb:83:in `block (3 levels) in ' 108s /tmp/autopkgtest-lxc.f1vq6prr/downtmp/build.NZh/src/test/integration/gem2deb_test.rb:87:in `instance_exec' 108s /tmp/autopkgtest-lxc.f1vq6prr/downtmp/build.NZh/src/test/integration/gem2deb_test.rb:87:in `block in create_test_from_should_hash' 108s === OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1068562: crmsh: autopkgtest regression: unsupported operand type(s) for -: 'NoneType' and 'int'
Source: crmsh
Version: 4.6.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it started to fail in
testing several days ago. Can you please investigate the situation and
fix it? I copied some of the output at the bottom of this report. This
looks like it will cause FTBFS too (I scheduled rebuilds on the
reproducible-builds infra to confirm).
The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing.
More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html
https://ci.debian.net/packages/c/crmsh/testing/amd64/44624510/
105s === FAILURES
===
105s __ TestUtils.test_findln_by_timestamp
__
105s
105s self = testMethod=test_findln_by_timestamp>
105s
105s def test_findln_by_timestamp(self):
105s target_time = "Apr 03 13:10"
105s target_time_stamp =
crmutils.parse_to_timestamp(target_time+' 2023')
105s with open('pacemaker.log') as f:
105s data = f.read()
105s constants.STAMP_TYPE = utils.determin_log_format(data)
105s pacemaker_file_path = "pacemaker.log"
105s result_line = utils.findln_by_timestamp(data,
target_time_stamp, pacemaker_file_path)
105s > result_line_stamp =
utils.get_timestamp(data.split('\n')[result_line-1], pacemaker_file_path)
105s E TypeError: unsupported operand type(s) for -: 'NoneType'
and 'int'
105s
105s test_report_utils.py:825: TypeError
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1066763: liferea: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
control: notfixed -1 1.15.5-1 On 04-04-2024 6:04 p.m., Paul Gevers wrote: So, marking the bug as not affecting the version in testing to avoid autoremoval. And also removing the fixed version. There was only a *time* that liferea was broken (by liblzma), not a version of liferea, nor was there a version that fixed the problem. Otherwise the BTS still thinks that the version in testing is affected and our tools schedule an autoremoval. Because of the time_t transition, liferea in unstable can't migrate soon. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1068363: src:autopkgtest: flaky autopkgtest (host dependent?) on ppc64el
The mystery continues. On 04-04-2024 10:08 p.m., Paul Gevers wrote: I forgot that on amd64, autopkgtest's autopkgtest now runs in qemu which doesn't benefit yet as much from tmpfs as lxc does, so it's not a good comparison. On ci-worker13: """ root@elbrus:/tmp/autopkgtest-lxc.ww6f2cls/downtmp/build.VWV/src# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 250G 44G 207G 18% / none492K 4.0K 488K 1% /dev tmpfs 126G 0 126G 0% /dev/shm tmpfs51G 52K 51G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock root@elbrus:/tmp/autopkgtest-lxc.ww6f2cls/downtmp/build.VWV/src# AUTOPKGTEST_TEST_SCHROOT=testing-amd64-sbuild tests/autopkgtest SchrootRunner.test_copy_timeout test_copy_timeout (__main__.SchrootRunner.test_copy_timeout) handling copying timeout ... ok -- Ran 1 test in 5.768s OK """ So it's not only tmpfs. I ran the test on ci-worker-ppc64el-05 (no other tests were running at the time) with adapted timeout. If I reduce the current 3 sec copy-timeout to 1 sec the test passes (2 seconds is too long, only int allowed). If I try the same thing in the opposite direction on ci-worker13, raising to 4 seconds causes failure in the """self.assertLess(huge_size, 100)""", with bumping to 5 seconds fails in the same way. ci-worker13 was running quite some tests at the same time, not sure if that's related. Anyways, it looks like we could just lower the timeout to 1 second and hope were fine for some time to come. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
