Bug#1072634: r-cran-testthat: autopkgtest regression in testing
Source: r-cran-testthat
Version: 3.2.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-02-27, r-cran-testthat's autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-testthat/testing/amd64/
105s ══ Failed tests
105s ── Error ('test-mock2.R:62:1'): can mock bindings in another
package ───
105s Error in `call_type(call)`: corrupt language object
105s ── Failure ('test-reporter-list.R:54:3'): exercise ListReporter
105s expectation_type(res[[4]]$results[[1]]) (`actual`) not identical
to "failure" (`expected`).
105s
105s `actual`: "warning"
105s `expected`: "failure"
105s ── Failure ('test-reporter-list.R:57:3'): exercise ListReporter
105s df$error (`actual`) not equal to c(FALSE, FALSE, FALSE, FALSE,
TRUE) (`expected`).
105s
105s `actual[2:5]`: FALSE FALSE FALSE FALSE
105s `expected[2:5]`: FALSE FALSE FALSE TRUE
105s ── Failure ('test-reporter-debug.R:51:3'): debug reporter is not
called for successes ──
105s get_frame_from_debug_reporter(2, success_fun) is not NULL
105s
105s `actual` is an environment
105s `expected` is NULL
105s ── Failure ('test-srcrefs.R:19:3'): line numbers captured for
expectations and warnings ──
105s `lines` (`actual`) not equal to c(2, 3) (`expected`).
105s
105s `actual`: 2 2 3
105s `expected`: 2 3
105s ── Failure ('test-srcrefs.R:32:3'): line numbers captured when
called indirectly ──
105s `lines` (`actual`) not equal to 4 (`expected`).
105s
105s `actual`: 4 4
105s `expected`: 4
105s ── Failure ('test-srcrefs.R:42:3'): line numbers captured when
called indirectly ──
105s `lines` (`actual`) not equal to 5 (`expected`).
105s
105s `actual`: 5 5
105s `expected`: 5
105s ── Failure ('test-srcrefs.R:51:3'): line numbers captured inside
a loop
105s `lines` (`actual`) not equal to rep(2, 4) (`expected`).
105s
105s `actual[2:8]`: 2 2 2 2 2 2 2
105s `expected[2:4]`: 2 2 2
105s ── Error ('test-test-that.R:55:5'): infinite recursion is
captured ─
105s
105s Error: evaluation nested too deeply: infinite recursion /
options(expressions=)?
105s Backtrace:
105s ▆
105s 1. ├─testthat::with_reporter(...) at test-test-that.R:54:3
105s 2. │ └─base::tryCatch(...)
105s 3. │ └─base (local) tryCatchList(expr, classes, parentenv, handlers)
105s 4. │ └─base (local) tryCatchOne(expr, names, parentenv, handlers[[1L]])
105s 5. │ └─base (local) doTryCatch(return(expr), name, parentenv, handler)
105s 6. ├─withr::with_options(...) at test-test-that.R:55:5
105s 7. │ └─base::force(code)
105s 8. ├─testthat::test_that(...)
105s 9. │ └─testthat::local_test_context()
105s 10. │ └─testthat::local_reproducible_output(.env = .env)
105s 11. │ └─withr::local_language(lang, .local_envir = .env)
105s 12. │ └─withr:::check_language_envvar("LC_ALL")
105s 13. │ └─base::warning(...)
105s 14. ├─base::.signalSimpleWarning(...)
105s 15. │ └─base::withRestarts(...)
105s 16. │ └─base (local) withOneRestart(expr, restarts[[1L]])
105s 17. │ └─base (local) doWithOneRestart(return(expr), restart)
105s 18. ├─testthat (local) ``(``)
105s 19. │ └─rlang::cnd_entrace(e)
105s 20. │ └─rlang::trace_back(top = top, bottom = bottom)
105s 21. │ └─rlang:::map(calls, call_zap_inline)
105s 22. │ └─base::lapply(.x, .f, ...)
105s 23. │ └─rlang (local) FUN(X[[i]], ...)
105s 24. └─rlang:::call_type_sum(x)
105s 25. ├─rlang::sym(sprintf("<%s>", rlang_type_sum(x)))
105s 26. │ └─rlang::is_symbol(x)
105s 27. ├─base::sprintf("<%s>", rlang_type_sum(x))
105s 28. └─rlang:::rlang_type_sum(x)
105s 29. └─rlang::is_installed("pillar")
105s 30. └─rlang:::detect_installed(info)
105s 31. ├─rlang:::list_c(...)
105s 32. │ └─rlang::inject(c(!!!x))
105s 33. │ └─rlang::enexpr(expr)
105s 34. └─rlang:::pmap(...)
105s 35. └─rlang:::.rlang_purrr_args_recycle(.l)
105s 36. └─rlang:::map_int(args, length)
105s 37. └─rlang:::.rlang_purrr_map_mold(.x, .f, integer(1), ...)
105s 38. └─base::vapply(.x, .f, .mold, ..., USE.NAMES = FALSE)
105s ── Failure ('test-test-that.R:102:3'): no braces required in
testthat 2e ───
105s `test_that("", expect_true(TRUE))` generated warnings:
105s * Changing language has no effect when envvar LC_ALL='C.UTF-8'
105s
105s [ FAIL 10 | WARN 1412 | SKIP 122 | PASS 819 ]
105s Deleting unused snapshots:
105s • R4.0/snapshot-file/version.txt
105s • R4.1/snapshot-file/version.txt
105s • R4.2/snapshot-file/version.txt
105s • R4.3/snapshot-file/version.txt
105s • snapshot-file/a.txt
105s • snapshot-file/foo.csv
105s • snapshot-file/foo.png
105s • snapshot-file/foo.r
105s • snapshot-file/secret.txt
106s Error: Test failures
106s Execution halted
Bug#1072632: r-cran-rsqlite: autopkgtest regression in testing
Source: r-cran-rsqlite
Version: 2.3.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-02-16, r-cran-rsqlite's autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-rsqlite/testing/amd64/
68s ══ Failed tests
68s ── Failure ('test-affinity.R:98:3'): affinity checks for dbFetch()
─
68s `expect_equal(class(dbFetch(rs, 1)$a), real_type)` threw an
unexpected warning.
68s Message: Changing language has no effect when envvar LC_ALL='C.UTF-8'
68s Class: simpleWarning/warning/condition
68s Backtrace:
68s ▆
68s 1. ├─... %>% expect_warning("coercing") at test-affinity.R:98:3
68s 2. ├─testthat::expect_warning(., "coercing")
68s 3. │ └─testthat:::expect_condition_matching(...)
68s 4. │ └─testthat:::quasi_capture(...)
68s 5. │ ├─testthat (local) .capture(...)
68s 6. │ │ └─base::withCallingHandlers(...)
68s 7. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 8. ├─testthat::expect_warning(., "coercing")
68s 9. │ └─testthat:::expect_condition_matching(...)
68s 10. │ └─testthat:::quasi_capture(...)
68s 11. │ ├─testthat (local) .capture(...)
68s 12. │ │ └─base::withCallingHandlers(...)
68s 13. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 14. ├─testthat::expect_warning(., "coercing")
68s 15. │ └─testthat:::expect_condition_matching(...)
68s 16. │ └─testthat:::quasi_capture(...)
68s 17. │ ├─testthat (local) .capture(...)
68s 18. │ │ └─base::withCallingHandlers(...)
68s 19. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 20. ├─testthat::expect_warning(., "coercing")
68s 21. │ └─testthat:::expect_condition_matching(...)
68s 22. │ └─testthat:::quasi_capture(...)
68s 23. │ ├─testthat (local) .capture(...)
68s 24. │ │ └─base::withCallingHandlers(...)
68s 25. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 26. ├─testthat::expect_warning(., "coercing")
68s 27. │ └─testthat:::expect_condition_matching(...)
68s 28. │ └─testthat:::quasi_capture(...)
68s 29. │ ├─testthat (local) .capture(...)
68s 30. │ │ └─base::withCallingHandlers(...)
68s 31. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 32. ├─testthat::expect_warning(., "coercing")
68s 33. │ └─testthat:::expect_condition_matching(...)
68s 34. │ └─testthat:::quasi_capture(...)
68s 35. │ ├─testthat (local) .capture(...)
68s 36. │ │ └─base::withCallingHandlers(...)
68s 37. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 38. ├─testthat::expect_warning(., "coercing")
68s 39. │ └─testthat:::expect_condition_matching(...)
68s 40. │ └─testthat:::quasi_capture(...)
68s 41. │ ├─testthat (local) .capture(...)
68s 42. │ │ └─base::withCallingHandlers(...)
68s 43. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 44. ├─testthat::expect_warning(., "coercing")
68s 45. │ └─testthat:::expect_condition_matching(...)
68s 46. │ └─testthat:::quasi_capture(...)
68s 47. │ ├─testthat (local) .capture(...)
68s 48. │ │ └─base::withCallingHandlers(...)
68s 49. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 50. └─RSQLite (local) check_affinity_fetch("BLOB", class(blob()),
class(blob()))
68s 51. ├─testthat::expect_warning(...) at test-affinity.R:60:3
68s 52. │ └─testthat:::expect_condition_matching(...)
68s 53. │ └─testthat:::quasi_capture(...)
68s 54. │ ├─testthat (local) .capture(...)
68s 55. │ │ └─base::withCallingHandlers(...)
68s 56. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 57. └─testthat::expect_equal(class(dbFetch(rs, 1)$a), real_type)
68s 58. └─testthat:::expect_waldo_equal("equal", act, exp, info, ...,
tolerance = tolerance)
68s 59. └─testthat:::waldo_compare(...)
68s 60. └─testthat:::local_reporter_output()
68s 61. └─reporter$local_user_output(.env)
68s 62. └─testthat::local_reproducible_output(...)
68s 63. └─withr::local_language(lang, .local_envir = .env)
68s 64. └─withr:::check_language_envvar("LC_ALL")
68s
68s [ FAIL 1 | WARN 842 | SKIP 8 | PASS 684 ]
68s Error: Test failures
68s In addition: Warning message:
68s call dbDisconnect() when finished working with a connection
68s Execution halted
Bug#1072631: r-cran-mockr: autopkgtest regression in testing
Source: r-cran-mockr
Version: 0.2.1-1
Severity: serious
Tags: trixie sid
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-03-01, r-cran-mockr's autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-mockr/testing/amd64/
76s == Failed tests
76s -- Failure ('test-mock.R:116:3'): empty or no-op mock
--
76s `expect_null(with_mock())` produced unexpected warnings.
76s Expected match: Not (?:mocking|evaluating) anything
76s Actual values:
76s * Not mocking anything. Please use named arguments to specify the
functions you want to mock.
76s * Not evaluating anything. Please use unnamed arguments to specify
expressions you want to evaluate.
76s * Changing language has no effect when envvar LC_ALL='C'
76s
76s [ FAIL 1 | WARN 27 | SKIP 0 | PASS 51 ]
76s Error: Test failures
76s Execution halted
Bug#1072630: r-cran-dplyr: autopkgtest regression in testing
Source: r-cran-dplyr
Version: 1.1.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-02-16, r-cran-dplyr's autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-dplyr/testing/amd64/
157s ══ Failed tests
157s ── Failure ('test-rows.R:161:3'): rows_update() works
──
157s `expect_identical(...)` produced warnings.
157s ── Failure ('test-rows.R:258:3'): rows_patch() works
───
157s `expect_identical(...)` produced warnings.
157s
157s [ FAIL 2 | WARN 5031 | SKIP 329 | PASS 2860 ]
159s Error: Test failures
159s Execution halted
Bug#1072629: r-cran-dials: autopkgtest regression in testing
Source: r-cran-dials
Version: 1.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-02-15, r-cran-dials' autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-dials/testing/amd64/
53s > library(testthat)
53s > library(dials)
53s Loading required package: scales
54s >
54s > if (requireNamespace("xml2")) {
54s + test_check("dials", reporter = MultiReporter$new(reporters =
list(JunitReporter$new(file = "test-results.xml"),
CheckReporter$new(
54s + } else {
54s + test_check("dials")
54s + }
54s Loading required namespace: xml2
54s Error in UseMethod("xml_add_child") :
54s no applicable method for 'xml_add_child' applied to an object of
class "NULL"
54s Calls: test_check ... o_apply -> lapply -> FUN -> ->
54s Execution halted
Bug#1072628: graphlan: autopkgtest regression in testing
Source: graphlan Version: 1.1.3-4 Severity: serious Tags: trixie sid User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2024-05-22, graphlan's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/g/graphlan/testing/amd64/ 43s Some packages could not be installed. This may mean that you have 43s requested an impossible situation or if you are using the unstable 43s distribution that some required packages have not yet been created 43s or been moved out of Incoming. 43s The following information may help to resolve the situation: 43s 43s The following packages have unmet dependencies: 43s satisfy:command-line : Depends: r-cran-randomfields but it is not installable 43s E: Unable to correct problems, you have held broken packages.
Bug#1071448: [Debian-med-packaging] Bug#1071448: marked as done (dipy: FTBFS on 32 bit archs with ArrayMemoryError)
Control: reopen -1 On Wed, 22 May 2024 at 15:36, Debian Bug Tracking System wrote: > dipy (1.9.0-3) unstable; urgency=medium > . >* Team upload. >* Skip the test_check_img_shapes on 32-bit systems. Closes: #1071448 Please also skip this test in the autopkgtest. Regards Graham
Bug#1071737: r-cran-data.table: autopkgtest regression on armhf
Source: r-cran-data.table Version: 1.15.4+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer r-cran-data.table's autopkgtest has regressed on armhf [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/r/r-cran-data.table/unstable/armhf/ 103s Test 2226.3 ran without errors but failed check that x equals y: 103s > x = DT[, prod(x, na.rm = TRUE), g] 103s g V1 [Key= Types=int,dou Classes=int,i64] 103s 1: 1 103s 2: 2 103s 3: 3 -8 103s > y = data.table(g = 1:3, V1 = as.integer64(c(NA, "9223372036854775807", -8L))) 103s g V1 [Key= Types=int,dou Classes=int,i64] 103s 1: 1 103s 2: 2 9223372036854775807 103s 3: 3 -8 103s Column 'V1': 'is.NA' value mismatch: 2 in current 1 in target 104s 104s Fri May 10 10:48:14 2024 endian==little, sizeof(long double)==8, longdouble.digits==, sizeof(pointer)==4, TZ==unset, Sys.timezone()=='Etc/UTC', Sys.getlocale()=='LC_CTYPE=C.UTF-8;LC_NUMERIC=C;LC_TIME=C.UTF-8;LC_COLLATE=C.UTF-8;LC_MONETARY=C.UTF-8;LC_MESSAGES=C.UTF-8;LC_PAPER=C.UTF-8;LC_NAME=C;LC_ADDRESS=C;LC_TELEPHONE=C;LC_MEASUREMENT=C.UTF-8;LC_IDENTIFICATION=C', l10n_info()=='MBCS=TRUE; UTF-8=TRUE; Latin-1=FALSE; codeset=UTF-8', getDTthreads()=='OpenMP version (_OPENMP)==201511; omp_get_num_procs()==16; R_DATATABLE_NUM_PROCS_PERCENT==unset (default 50); R_DATATABLE_NUM_THREADS==unset; R_DATATABLE_THROTTLE==unset (default 1024); omp_get_thread_limit()==2147483647; omp_get_max_threads()==16; OMP_THREAD_LIMIT==unset; OMP_NUM_THREADS==unset; RestoreAfterFork==true; data.table is using 8 threads with throttle==1024. See ?setDTthreads.', zlibVersion()==1.3 ZLIB_VERSION==1.3 104s Error: 1 error(s) out of 9678. Search tests/tests.Rraw.bz2 for test number(s) 2226.3. Duration: 30.5s elapsed (31.4s cpu). 104s Execution halted
Bug#1071683: confget: autopkgtest regression in testing
Source: confget Version: 5.1.2-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2024-02-27, confget's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/c/confget/testing/amd64/ 95s autopkgtest [19:08:12]: test feature-check: [--- 95s error: unexpected argument '-q' found 95s 95s tip: to pass '-q' as a value, use '-- -q' 95s 95s Usage: feature-check [OPTIONS] [EXPRESSIONS]... 95s autopkgtest [19:08:12]: test feature-check: ---]
Bug#1071667: r-cran-bbmle: autopkgtest regression on ppc64el
Source: r-cran-bbmle Version: 1.0.25.1-1 User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2024-04-18, r-cran-bbmle's autopkgtest regressed in testing on ppc64el [1]. I've copied what I hope is the relevant part of a recent log below. This appears only to be a warning, it would be good if this could be filtered out somehow. Regards Graham [1] https://ci.debian.net/packages/r/r-cran-bbmle/testing/ppc64el/ 72s --- profbound.Rout.save_ 2024-05-23 12:58:07.420821085 + 72s +++ profbound.Rout_ 2024-05-23 12:58:07.424820960 + 72s @@ -40,6 +40,9 @@ 72s + method="L-BFGS-B") 72s > 72s > pp <- profile(fit2,prof.lower=-0.2) 72s +Warning message: 72s +In mle2(minuslogl = function (a = NULL, b = NULL) : 72s + convergence failure: code=52 (ERROR: ABNORMAL_TERMINATION_IN_LNSRCH) 72s > stopifnot(min(subset(as.data.frame(pp),param=="b")$par.vals.b)==-0.2) 72s > ## note that b does go below -0.2 when profiling a ... 72s > options(old_opt) 72s autopkgtest [12:58:07]: test run-unit-test: ---] 72s run-unit-test FAIL non-zero exit status 1
Bug#1069509: r-cran-metamix: FTBFS on armhf: tests fail
Control: severity -1 important Control: tags -1 + moreinfo While r-cran-metamix did fail on armhf [1] and i386 [2] around the time of your bug report, it is passing now. [1] https://tests.reproducible-builds.org/debian/history/armhf/r-cran-metamix.html [2] https://tests.reproducible-builds.org/debian/history/i386/r-cran-metamix.html
Bug#1071523: r-cran-spatstat.geom: autopkgtest regression in testing
Source: r-cran-spatstat.geom Version: 3.2-7-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2023-11-27, r-cran-spatstat.geom's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/r/r-cran-spatstat.geom/testing/amd64/ 55s Some packages could not be installed. This may mean that you have 55s requested an impossible situation or if you are using the unstable 55s distribution that some required packages have not yet been created 55s or been moved out of Incoming. 55s The following information may help to resolve the situation: 55s 55s The following packages have unmet dependencies: 55s autopkgtest-satdep : Depends: r-cran-spatstat.core but it is not installable 55s E: Unable to correct problems, you have held broken packages. 55s autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs 55s Reading package lists... 55s Building dependency tree... 55s Reading state information... 55s E: Unable to locate package r-cran-spatstat.core 55s E: Couldn't find any package by glob 'r-cran-spatstat.core' 55s E: Couldn't find any package by regex 'r-cran-spatstat.core' 55s pkg-r-autopkgtest FAIL badpkg 55s blame: r-cran-spatstat.geom 55s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
Bug#1067842: transition: octave-9
Hi Sébastien octave-fits FTBFS on all architectures (#1070956), and octave-stk FTBFS on 32-bit architectures (#1069477), would you please take a look? Regards Graham
Bug#1071255: numpy: FTBFS with Python 3.12 as default
Source: numpy
Version: 1:1.26.4+ds-9
Severity: important
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
Hi Maintainer
numpy FTBFS with Python 3.12 as the default version (i.e. with
python3-defaults/3.12.1-1 from experimental).
I've copied what I hope is the relevant part of the log below.
Regards
Graham
LANG=C sphinx-build -b html -T --keep-going -d build/doctrees source
build/html
Running Sphinx v7.2.6
/usr/lib/python3/dist-packages/breathe/project.py:116:
RemovedInSphinx80Warning: Sphinx 8 will drop support for representing
paths as strings. Use "pathlib.Path" or "os.fspath" instead.
self._default_build_dir = os.path.dirname(app.doctreedir.rstrip(os.sep))
1.26 1.26.4
[autosummary] generating autosummary for: benchmarking.rst,
dev/alignment.rst, dev/depending_on_numpy.rst,
dev/development_advanced_debugging.rst,
dev/development_environment.rst, dev/development_workflow.rst,
dev/gitwash/configure_git.rst, dev/gitwash/development_setup.rst,
dev/gitwash/dot2_dot3.rst, dev/gitwash/following_latest.rst, ...,
user/how-to-verify-bug.rst, user/howtos_index.rst, user/index.rst,
user/install.rst, user/misc.rst, user/numpy-for-matlab-users.rst,
user/quickstart.rst, user/theory.broadcasting.rst,
user/troubleshooting-importerror.rst, user/whatisnumpy.rst
WARNING: Failed to import numpy.distutils.misc_util.
Possible hints:
* AttributeError: module 'numpy' has no attribute 'distutils'
* ModuleNotFoundError: No module named 'numpy.distutils'
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/sphinx/ext/autosummary/generate.py",
line 503, in generate_autosummary_docs
name, obj, parent, modname = import_by_name(entry.name)
^^
File "/usr/lib/python3/dist-packages/sphinx/ext/autosummary/__init__.py",
line 655, in import_by_name
raise ImportExceptionGroup('no module named %s' % ' or
'.join(tried), exceptions)
sphinx.ext.autosummary.ImportExceptionGroup: no module named
numpy.distutils.ccompiler
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/sphinx/events.py", line 97, in emit
results.append(listener.handler(self.app, *args))
^
File "/usr/lib/python3/dist-packages/sphinx/ext/autosummary/__init__.py",
line 814, in process_generate_options
generate_autosummary_docs(genfiles, suffix=suffix, base_path=app.srcdir,
File "/usr/lib/python3/dist-packages/sphinx/ext/autosummary/generate.py",
line 508, in generate_autosummary_docs
name, obj, parent, modname = import_ivar_by_name(entry.name)
^^^
File "/usr/lib/python3/dist-packages/sphinx/ext/autosummary/__init__.py",
line 712, in import_ivar_by_name
real_name, obj, parent, modname = import_by_name(name, prefixes)
^^
File "/usr/lib/python3/dist-packages/sphinx/ext/autosummary/__init__.py",
line 655, in import_by_name
raise ImportExceptionGroup('no module named %s' % ' or
'.join(tried), exceptions)
sphinx.ext.autosummary.ImportExceptionGroup: no module named numpy.distutils
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/sphinx/cmd/build.py", line 293,
in build_main
app = Sphinx(args.sourcedir, args.confdir, args.outputdir,
File "/usr/lib/python3/dist-packages/sphinx/application.py", line
271, in __init__
self._init_builder()
File "/usr/lib/python3/dist-packages/sphinx/application.py", line
342, in _init_builder
self.events.emit('builder-inited')
File "/usr/lib/python3/dist-packages/sphinx/events.py", line 108, in emit
raise ExtensionError(__("Handler %r for event %r threw an exception") %
sphinx.errors.ExtensionError: Handler for event 'builder-inited'
threw an exception (exception: no module named numpy.distutils)
Extension error (sphinx.ext.autosummary):
Handler for
event 'builder-inited' threw an exception (exception: no module named
numpy.distutils)
make[2]: *** [Makefile:154: html-build] Error 2
make[2]: Leaving directory '/<>/doc'
make[1]: *** [debian/rules:86: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:72: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
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: severity -1 important Control: tags -1 + unreproducible Reproducible builds [1] shows a failure on 2024-03-02, but is successful now. [1] https://tests.reproducible-builds.org/debian/history/armhf/gpaw.html
Bug#1069510: elpa: FTBFS on armhf: make[5]: *** [Makefile:84371: test-suite.log] Error 1
Control: severity -1 important Control: tags -1 + unreproducible Reproducible builds [1] shows failures on 2024-04-06 and 2024-04-25, but is successful now. [1] https://tests.reproducible-builds.org/debian/history/armhf/elpa.html
Bug#1071174: onionshare: runtime dependency on cython
Package: src:nionshare Version: 2.6.2-1 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: cython-rt-dep [This bug is targeted to the upcoming trixie release] The package build-depends on cython3 or cython3-legacy, and one of the built binary packages also depends on cython3 or cython3-legacy. That might be correct, but in most cases there is no runtime dependency for a tool like cython, that is only used when building the package. Please check that this dependency can be removed. Most likely this dependency is generated by pybuild, because the setup.py requires Cython in it's 'install_requires' attribute. Please remove that, after checking that it is not a runtime dependency, and also report that issue upstream for upcoming releases. If the runtime dependency is necessary, please just close this bug report.
Bug#1071171: r-cran-mertools: autopkgtest regression on i386 with rmatrix 1.7-0
Source: r-cran-mertools
Version: 0.6.2-1
Severity: serious
X-Debbugs-Cc: Dirk Eddelbuettel
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
r-cran-mertools' autopkgtest regresses on i386 when tested with
rmatrix 1.7-0 [1]. I've copied what I hope is the relevant part of
the log below.
Additionally, r-cran-mertools' autopkgtests run for almost 3 hours and
time out when tested with lme4 4 1.1-35.3.
Regards
Graham
[1] hhttps://ci.debian.net/packages/r/r-cran-mertools/testing/i386/
108s Error in `private$handle_error()`:
108s ! testthat subprocess exited in file `test-merData.R`
108s Caused by error:
108s ! R session crashed with exit code -6
108s Backtrace:
108s x
108s 1. \-testthat::test_check("merTools", filter = "^[a-m]")
108s 2. \-testthat::test_dir(...)
108s 3. \-testthat:::test_files(...)
108s 4. \-testthat:::test_files_parallel(...)
108s 5. +-withr::with_dir(...)
108s 6. | \-base::force(code)
108s 7. +-testthat::with_reporter(...)
108s 8. | \-base::tryCatch(...)
108s 9. | \-base (local) tryCatchList(expr, classes, parentenv, handlers)
108s 10. | \-base (local) tryCatchOne(expr, names, parentenv, handlers[[1L]])
108s 11. | \-base (local) doTryCatch(return(expr), name, parentenv, handler)
108s 12. \-testthat:::parallel_event_loop_chunky(queue, reporters, ".")
108s 13. \-queue$poll(Inf)
108s 14. \-base::lapply(...)
108s 15. \-testthat (local) FUN(X[[i]], ...)
108s 16. \-private$handle_error(msg, i)
108s 17. \-rlang::abort(...)
108s Execution halted
Bug#1071170: r-cran-mertools: autopkgtest regression on i386 with rmatrix 1.7-0
Source: r-bioc-mertools
Version: 0.6.2-1
Severity: serious
X-Debbugs-Cc: Dirk Eddelbuettel
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
r-cran-mertools' autopkgtest regresses on i386 when tested with
rmatrix 1.7-0 [1]. I've copied what I hope is the relevant part of
the log below.
Additionally, r-cran-mertools' autopkgtests run for almost 3 hours and
time out when tested with lme4 4 1.1-35.3.
Regards
Graham
[1] hhttps://ci.debian.net/packages/r/r-cran-mertools/testing/i386/
108s Error in `private$handle_error()`:
108s ! testthat subprocess exited in file `test-merData.R`
108s Caused by error:
108s ! R session crashed with exit code -6
108s Backtrace:
108s x
108s 1. \-testthat::test_check("merTools", filter = "^[a-m]")
108s 2. \-testthat::test_dir(...)
108s 3. \-testthat:::test_files(...)
108s 4. \-testthat:::test_files_parallel(...)
108s 5. +-withr::with_dir(...)
108s 6. | \-base::force(code)
108s 7. +-testthat::with_reporter(...)
108s 8. | \-base::tryCatch(...)
108s 9. | \-base (local) tryCatchList(expr, classes, parentenv, handlers)
108s 10. | \-base (local) tryCatchOne(expr, names, parentenv, handlers[[1L]])
108s 11. | \-base (local) doTryCatch(return(expr), name, parentenv, handler)
108s 12. \-testthat:::parallel_event_loop_chunky(queue, reporters, ".")
108s 13. \-queue$poll(Inf)
108s 14. \-base::lapply(...)
108s 15. \-testthat (local) FUN(X[[i]], ...)
108s 16. \-private$handle_error(msg, i)
108s 17. \-rlang::abort(...)
108s Execution halted
Bug#1071106: r-cran-sf: autopkgtest regression in testing
Source: r-cran-sf Version: 1.0-16+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime after 2023-11-10, r-cran-sf's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/r/r-cran-sf/testing/amd64/ 154s Some packages could not be installed. This may mean that you have 154s requested an impossible situation or if you are using the unstable 154s distribution that some required packages have not yet been created 154s or been moved out of Incoming. 154s The following information may help to resolve the situation: 154s 154s The following packages have unmet dependencies: 154s autopkgtest-satdep : Depends: r-cran-spatstat.core but it is not installable 154s E: Unable to correct problems, you have held broken packages. 154s autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs 154s Reading package lists... 154s Building dependency tree... 154s Reading state information... 154s E: Unable to locate package r-cran-spatstat.core 154s E: Couldn't find any package by glob 'r-cran-spatstat.core' 154s E: Couldn't find any package by regex 'r-cran-spatstat.core' 154s pkg-r-autopkgtest FAIL badpkg 154s blame: r-cran-sf 154s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
Bug#1071104: r-cran-performance: autopkgtest regression in testing
Source: r-cran-performance Version: 0.10.8-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime after 2024-02-08, r-cran-performance's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/r/r-cran-performance/testing/amd64/ 14s The following packages have unmet dependencies: 14s autopkgtest-satdep : Depends: r-cran-estimatr but it is not installable 14s E: Unable to correct problems, you have held broken packages. 14s autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs 14s run-unit-test FAIL badpkg 14s blame: r-cran-performance 14s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
Bug#1067842: transition: octave-9
Hi Sébastien On Sat, 11 May 2024 at 08:48, Sébastien Villemot wrote: > Thanks. Uploaded and built on all release architectures. binNMUs underway! Regards Graham
Bug#1063358: c-blosc2 tests fail with bus errors on armhf
Control: tags -1 + patch fixed-upstream This was fixed in Ubuntu and the patch forwarded upstream; https://github.com/Blosc/c-blosc2/pull/588
Bug#1070843: r-bioc-s4vectors: autopkgtest regression with r-base 4.4.0
Source: r-bioc-s4vectors
Version: 0.40.2+dfsg-1
Severity: serious
X-Debbugs-Cc: Dirk Eddelbuettel
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
r-bioc-s4vectors' autopkgtest regresses when tested with r-base 4.4.0
[1]. I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-bioc-s4vectors/testing/amd64/
125s > S4Vectors:::.test()
129s Timing stopped at: 0.009 0 0.009
129s Error in var(x) : is.atomic(y) is not TRUE
129s In addition: Warning messages:
129s 1: In combineUniqueCols(X, Y, Z, use.names = FALSE) :
129s different values in multiple instances of column 'dup', ignoring this
129s column in DFrame 2
129s 2: In combineUniqueCols(X, Y, Z) :
129s different values for shared rows in multiple instances of column 'dup',
129s ignoring this column in DFrame 2
129s 3: In combineUniqueCols(x, y2) :
129s different values for shared rows in multiple instances of column 'X',
129s ignoring this column in DFrame 2
130s Loading required package: GenomeInfoDb
132s
132s
132s RUNIT TEST PROTOCOL -- Thu May 9 22:12:10 2024
132s ***
132s Number of test functions: 74
132s Number of errors: 1
132s Number of failures: 0
132s
132s
132s 1 Test Suite :
132s S4Vectors RUnit Tests - 74 test functions, 1 error, 0 failures
132s ERROR in test_Rle_numerical: Error in var(x) : is.atomic(y) is not TRUE
132s
132s Test files with failing tests
132s
132s test_Rle-utils.R
132s test_Rle_numerical
132s
132s
132s Error in BiocGenerics:::testPackage("S4Vectors") :
132s unit tests failed for package S4Vectors
132s Calls: ->
132s Execution halted
Bug#1070841: r-bioc-iranges: autopkgtest regression with r-base 4.4.0
Source: r-bioc-iranges Version: 2.36.0-1 Severity: serious X-Debbugs-Cc: Dirk Eddelbuettel User: debian...@lists.debian.org Usertags: regression Hi Maintainer r-bioc-iranges' autopkgtest regresses when tested with r-base 4.4.0 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/r/r-bioc-iranges/testing/amd64/ 194s *** 194s Number of test functions: 98 194s Number of errors: 1 194s Number of failures: 0 194s 194s 194s 1 Test Suite : 194s IRanges RUnit Tests - 98 test functions, 1 error, 0 failures 194s ERROR in test_AtomicList_numerical: Error in FUN(X[[i]], ...) : is.atomic(y) is not TRUE 194s 194s Test files with failing tests 194s 194s test_AtomicList-utils.R 194s test_AtomicList_numerical 194s 194s 194s Warning messages: 194s 1: In recycleListElements(e1, en) : 194s Some element lengths are not multiples of their corresponding element length in e1 194s 2: In x + y : 194s longer object length is not a multiple of shorter object length 194s 3: In recycleListElements(e1, en) : 194s Some element lengths are not multiples of their corresponding element length in e1 194s 4: In x + y : 194s longer object length is not a multiple of shorter object length 194s Execution halted
Bug#1070842: r-bioc-mutationalpatterns: autopkgtest regression with r-base 4.4.0
Source: r-bioc-mutationalpatterns
Version: 3.12.0+dfsg-1
Severity: serious
X-Debbugs-Cc: Dirk Eddelbuettel
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
r-bioc-mutationalpatterns' autopkgtest regresses when tested with r-base 4.4.0
[1]. I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-bioc-mutationalpatterns/testing/amd64/
125s > test_check("MutationalPatterns")
172s [ FAIL 3 | WARN 275 | SKIP 0 | PASS 280 ]
172s
172s ══ Failed tests
172s ── Error ('test-fit_to_signatures_bootstrapped.R:12:3'): Output
has correct class ──
172s Error in `FUN(X[[i]], ...)`: isEmpty() is not defined for objects
of class NULL
172s Backtrace:
172s ▆
172s 1. ├─MutationalPatterns::fit_to_signatures_bootstrapped(...) at
test-fit_to_signatures_bootstrapped.R:12:3
172s 2. │ └─MutationalPatterns::fit_to_signatures_strict(...)
172s 3. │ └─MutationalPatterns:::.strict_refit_backwards_selection_sample(...)
172s 4. │ └─MutationalPatterns:::.plot_sim_decay(...)
172s 5. │ ├─sims[!S4Vectors::isEmpty(sims)] %>% unlist()
172s 6. │ ├─S4Vectors::isEmpty(sims)
172s 7. │ └─S4Vectors::isEmpty(sims)
172s 8. │ └─base::vapply(x, isEmpty, logical(1L))
172s 9. │ ├─S4Vectors (local) FUN(X[[i]], ...)
172s 10. │ └─S4Vectors (local) FUN(X[[i]], ...)
172s 11. └─base::unlist(.)
172s ── Error ('test-fit_to_signatures_bootstrapped.R:31:3'): Output
is equal to expected ──
172s Error in `FUN(X[[i]], ...)`: isEmpty() is not defined for objects
of class NULL
172s Backtrace:
172s ▆
172s 1. ├─MutationalPatterns::fit_to_signatures_bootstrapped(...) at
test-fit_to_signatures_bootstrapped.R:31:3
172s 2. │ └─MutationalPatterns::fit_to_signatures_strict(...)
172s 3. │ └─MutationalPatterns:::.strict_refit_backwards_selection_sample(...)
172s 4. │ └─MutationalPatterns:::.plot_sim_decay(...)
172s 5. │ ├─sims[!S4Vectors::isEmpty(sims)] %>% unlist()
172s 6. │ ├─S4Vectors::isEmpty(sims)
172s 7. │ └─S4Vectors::isEmpty(sims)
172s 8. │ └─base::vapply(x, isEmpty, logical(1L))
172s 9. │ ├─S4Vectors (local) FUN(X[[i]], ...)
172s 10. │ └─S4Vectors (local) FUN(X[[i]], ...)
172s 11. └─base::unlist(.)
172s ── Error ('test-fit_to_signatures_strict.R:11:1'): (code run
outside of `test_that()`) ──
172s Error in `FUN(X[[i]], ...)`: isEmpty() is not defined for objects
of class NULL
172s Backtrace:
172s ▆
172s 1. ├─MutationalPatterns::fit_to_signatures_strict(...) at
test-fit_to_signatures_strict.R:11:1
172s 2. │ └─MutationalPatterns:::.strict_refit_backwards_selection_sample(...)
172s 3. │ └─MutationalPatterns:::.plot_sim_decay(...)
172s 4. │ ├─sims[!S4Vectors::isEmpty(sims)] %>% unlist()
172s 5. │ ├─S4Vectors::isEmpty(sims)
172s 6. │ └─S4Vectors::isEmpty(sims)
172s 7. │ └─base::vapply(x, isEmpty, logical(1L))
172s 8. │ ├─S4Vectors (local) FUN(X[[i]], ...)
172s 9. │ └─S4Vectors (local) FUN(X[[i]], ...)
172s 10. └─base::unlist(.)
172s
172s [ FAIL 3 | WARN 275 | SKIP 0 | PASS 280 ]
173s Error: Test failures
173s Execution halted
Bug#1070840: r-cran-ff: autopkgtest regression with r-base 4.4.0
Source: r-cran-ff
Version: 4.0.12+ds-1
Severity: serious
X-Debbugs-Cc: Dirk Eddelbuettel
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
r-cran-ff's autopkgtest regresses when tested with r-base 4.4.0 [1].
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-ff/testing/amd64/
42s ══ Failed tests
42s ── Failure ('test-zero_lengths.R:34:3'): file size is correct when
creating ff integer from scratch ──
42s file.exists(f1) is not TRUE
42s
42s `actual`: FALSE
42s `expected`: TRUE
42s
42s [ FAIL 1 | WARN 52 | SKIP 0 | PASS 965 ]
42s Error: Test failures
42s Execution halted
Bug#1070839: r-cran-data.table: autopkgtest regression on i386
Source: r-cran-data.table Version: 1.15.4+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer r-cran-data.table's autopkgtest has regressed on i386 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/r/r-cran-data.table/testing/i386/ 104s Test 2150.025 produced 0 warnings but expected 1 104s Expected: datetimes before 1902 may not be accurate: warns once per session 104s Observed: 109s 109s Fri May 10 06:13:18 2024 endian==little, sizeof(long double)==12, longdouble.digits==64, sizeof(pointer)==4, TZ==unset, Sys.timezone()=='Etc/UTC', Sys.getlocale()=='LC_CTYPE=C.UTF-8;LC_NUMERIC=C;LC_TIME=C.UTF-8;LC_COLLATE=C.UTF-8;LC_MONETARY=C.UTF-8;LC_MESSAGES=C.UTF-8;LC_PAPER=C.UTF-8;LC_NAME=C;LC_ADDRESS=C;LC_TELEPHONE=C;LC_MEASUREMENT=C.UTF-8;LC_IDENTIFICATION=C', l10n_info()=='MBCS=TRUE; UTF-8=TRUE; Latin-1=FALSE; codeset=UTF-8', getDTthreads()=='OpenMP version (_OPENMP)==201511; omp_get_num_procs()==2; R_DATATABLE_NUM_PROCS_PERCENT==unset (default 50); R_DATATABLE_NUM_THREADS==unset; R_DATATABLE_THROTTLE==unset (default 1024); omp_get_thread_limit()==2147483647; omp_get_max_threads()==2; OMP_THREAD_LIMIT==unset; OMP_NUM_THREADS==unset; RestoreAfterFork==true; data.table is using 1 threads with throttle==1024. See ?setDTthreads.', zlibVersion()==1.3 ZLIB_VERSION==1.3 109s Error: 1 error(s) out of 9702. Search tests/tests.Rraw.bz2 for test number(s) 2150.025. Duration: 35.0s elapsed (34.1s cpu). 109s Execution halted
Bug#1067842: transition: octave-9
Control: tags -1 + confirmed Hi Sébastien On Thu, 9 May 2024 at 08:09, Sebastian Ramacher wrote: > plplot is involved in the gnat and octave transitions. So let's do this > one after gnat is done. gnat 13 has migrated, please go ahead. Regards Graham
Bug#1070746: Bug#1065309: transition: gnat (12 -> 13 + time_t64)
Hi Rafael and Nicolas On Wed, 8 May 2024 at 19:58, Rafael Laboissière wrote: > I will soon upload version 5.15.0+dfsg2-11, with the fix proposed by > Nicolas in Bug#1070746. Thanks for the quick turnaround! gnat 13 has migrated. Regards Graham
Bug#1065309: transition: gnat (12 -> 13 + time_t64)
Hi Nicolas and Rafael It looks like the last blocker for this transition is plplot 5.15.0+dfsg2-10 failing its own autopkgtests [1]. Regards Graham [1] https://ci.debian.net/packages/p/plplot/
Bug#1018336: deap: build-depends on python3-nose or uses it for autopkgtest
Control: reopen -1 Control: severity -1 serious deap 1.4.1-1 still depends on python3-nose for its autopkgtests. However, these are currently failing, preventing migration to testing. debian/tests/control contains: Depends: python3-all, python3-deap, python3-numpy, python3-nose At least python3-nose should probably be replaced by python3-pytest
Bug#1070515: dipy: FTBFS with nocheck profile
Source: dipy Version: 1.8.0-2 Severity: serious Tags: ftbfs patch Hi Maintainer dipy FTBFS when built with the 'nocheck' profile. I've copied what I hope is the relevant part of the log below. The following patch worked for me: --- a/debian/rules +++ b/debian/rules @@ -111,11 +111,11 @@ ; done endif # Cleanup files landing unnecessarily in the python3 modules directory. - rm -v debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/*.nii.gz - rm -v debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/*.trk - rm -v debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/affine.txt + rm -fv debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/*.nii.gz + rm -fv debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/*.trk + rm -fv debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/affine.txt # Cleanup files landing in non-standard path - rm -rv debian/$(PACKAGE3_NAME)/usr/doc + rm -rfv debian/$(PACKAGE3_NAME)/usr/doc ## "Instantiate" both rules so dh sees them override_dh_python3: @@ -136,9 +136,9 @@ -X.par -X.bin -Xobjects.inv execute_before_dh_link-indep: - rm -v debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/doctools.js - rm -v debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/language_data.js - rm -v debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/searchtools.js + rm -fv debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/doctools.js + rm -fv debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/language_data.js + rm -fv debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/searchtools.js execute_after_dh_fixperms-arch: # Fix a couple of executables neither elf nor scripts. Regards Graham find debian/ -name LICENSE -delete # Only now lets build docs # Run tests later on # cd build to prevent use of local/not-built source tree # Cleanup files landing unnecessarily in the python3 modules directory. rm -v debian/python3-dipy/usr/lib/python3*/dist-packages/*.nii.gz rm: cannot remove 'debian/python3-dipy/usr/lib/python3*/dist-packages/*.nii.gz': No such file or directory make[1]: *** [debian/rules:81: execute_after_dh_auto_install] Error 1
Bug#1070480: deap: FTBFS with Python 3.12 as default
Source: deap Version: 1.3.1-5 Severity: important Tags: ftbfs patch User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer deap FTBFS with Python 3.12 as the default version (i.e. with python3-defaults/3.12.1-1 from experimental). I've copied what I hope is the relevant part of the log below. If deap really still needs lib2to3, then please add an explicit build-dependency. The following patch worked for me: --- a/debian/control +++ b/debian/control @@ -7,6 +7,7 @@ debhelper-compat (= 12), dh-python, python3-all-dev, + python3-lib2to3, python3-setuptools, python3-nose, python3-numpy, Regards Graham I: pybuild pybuild:334: python3.12 -m lib2to3 --write --nobackups --no-diffs /<>/.pybuild/cpython3_3.12_deap/build /usr/bin/python3.12: No module named lib2to3
Bug#1070446: rocm-hipamd: arm64 FTBFS with glibc 2.38
Source: rocm-hipamd Version: 5.7.1-3 Severity: serious Tags: ftbfs Hi Maintainer As can be seen in reproducible builds [1], rocm-hipamd FTBFS on arm64 with glibc 2.38. I've copied what I hope is the relevant part of the log below. A bug was filed against glibc [2], but it seems glibc upstream do not consider it a bug in glibc. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/rocm-hipamd.html [2] https://sourceware.org/bugzilla/show_bug.cgi?id=30909 In file included from /tmp/hip_pch.724714/hip_pch.h:1: In file included from /build/reproducible-path/rocm-hipamd-5.7.1/hip/include/hip/hip_runtime.h:62: In file included from /build/reproducible-path/rocm-hipamd-5.7.1/hipamd/include/hip/amd_detail/amd_hip_runtime.h:76: In file included from /usr/lib/gcc/aarch64-linux-gnu/13/../../../../include/c++/13/cmath:47: In file included from /usr/include/math.h:40: /usr/include/aarch64-linux-gnu/bits/math-vector.h:40:9: error: unknown type name '__SVFloat32_t' 40 | typedef __SVFloat32_t __sv_f32_t; | ^ /usr/include/aarch64-linux-gnu/bits/math-vector.h:41:9: error: unknown type name '__SVFloat64_t' 41 | typedef __SVFloat64_t __sv_f64_t; | ^ /usr/include/aarch64-linux-gnu/bits/math-vector.h:42:9: error: unknown type name '__SVBool_t' 42 | typedef __SVBool_t __sv_bool_t; | ^ 3 errors generated when compiling for . CMake Error at hipamd/src/CMakeLists.txt:182 (message): Failed to embed PCH
Bug#1070444: cxref: arm64 FTBFS with glibc 2.38
Source: cxref
Version: 1.6e-5
Severity: serious
Tags: ftbfs trixie sid
Hi Maintainer
As can be seen in reproducible builds [1], cxref FTBFS on arm64 with
glibc 2.38. I've copied what I hope is the relevant part of the log
below.
A bug was filed against glibc [2], but it seems glibc upstream do not
consider it a bug in glibc.
Regards
Graham
[1] https://tests.reproducible-builds.org/debian/rb-pkg/cxref.html
[2] https://sourceware.org/bugzilla/show_bug.cgi?id=30909
../src/cxref -D_Float128='long double' -O. -NREADME-TMP -xref README.c
/usr/include/aarch64-linux-gnu/bits/math-vector.h:30: cxref: syntax error
The previous 10, current and next 10 symbols are:
-10 | 258 : IDENTIFIER : __overflow
-9 | 40 : '(' : (
-8 | 259 :TYPE_NAME : FILE
-7 | 42 : '*' : *
-6 | 44 : ',' : ,
-5 | 296 : INT : int
-4 | 41 : ')' : )
-3 | 59 : ';' : ;
-2 | 285 : TYPEDEF : typedef
-1 | 258 : IDENTIFIER : __Float32x4_t
0 | 258 : IDENTIFIER : __f32x4_t
1 | 59 : ';' : ;
2 | 285 : TYPEDEF : typedef
3 | 258 : IDENTIFIER : __Float64x2_t
4 | 258 : IDENTIFIER : __f64x2_t
5 | 59 : ';' : ;
6 | 285 : TYPEDEF : typedef
7 | 258 : IDENTIFIER : __SVFloat32_t
8 | 258 : IDENTIFIER : __sv_f32_t
9 | 59 : ';' : ;
10 | 285 : TYPEDEF : typedef
Bug#1070443: aspectc++: arm64 FTBFS with glibc 2.38
Source: aspectc++ Version: 1:2.3+git20230726-1 Severity: serious Tags: ftbfs Hi Maintainer As can be seen in reproducible builds [1], aspectc++ FTBFS on arm64 with glibc 2.38. I've copied what I hope is the relevant part of the log below. A bug was filed against glibc [2], but it seems glibc upstream do not consider it a bug in glibc. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/aspectc++.html [2] https://sourceware.org/bugzilla/show_bug.cgi?id=30909 Weaving aspects into PreExprParser.cc... Weaving aspects into PreParser.cc... Generating library header files... In file included from cpp/PreExprParser.lem:56: In file included from /usr/include/c++/13/math.h:36: In file included from /usr/include/c++/13/cmath:47: In file included from /usr/include/math.h:40: /usr/include/aarch64-linux-gnu/bits/math-vector.h:30:9: error: unknown type name '__Float32x4_t' typedef __Float32x4_t __f32x4_t; ^ /usr/include/aarch64-linux-gnu/bits/math-vector.h:31:9: error: unknown type name '__Float64x2_t' typedef __Float64x2_t __f64x2_t; ^
Bug#1070442: indexed-gzip: FTBFS with Python 3.12 as default
Source: indexed-gzip
Version: 1.7.0-1.1
Severity: important
Tags: ftbfs patch
User: debian-pyt...@lists.debian.org
Usertags: python3.12
Hi Maintainer
indexed-gzip FTBFS with Python 3.12 as the default version (i.e. with
python3-defaults/3.12.1-1 from experimental).
I've copied what I hope is the relevant part of the log below.
Please see the upstream issue [1], which is linked to the commit where
this is fixed.
Regards
Graham
[1] https://github.com/pauldmccarthy/indexed_gzip/issues/125
=== FAILURES ===
test_picklable
@pytest.mark.slow_test
def test_picklable():
> ctest_indexed_gzip.test_picklable()
../indexed_gzip/tests/test_indexed_gzip.py:177:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
indexed_gzip/tests/ctest_indexed_gzip.pyx:1045: in
indexed_gzip.tests.ctest_indexed_gzip.test_picklable
???
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> ???
E TypeError: cannot pickle 'IndexedGzipFile' instances
indexed_gzip/tests/ctest_indexed_gzip.pyx:1055: TypeError
- Captured stdout call -
Compressing data with a single call to gzip ... test.gz
Waiting (1.00 minutes)
Waiting (1.00 minutes)
test_copyable _
def test_copyable():
> ctest_indexed_gzip.test_copyable()
../indexed_gzip/tests/test_indexed_gzip.py:180:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
indexed_gzip/tests/ctest_indexed_gzip.pyx:1088: in
indexed_gzip.tests.ctest_indexed_gzip.test_copyable
???
indexed_gzip/tests/ctest_indexed_gzip.pyx:1096: in
indexed_gzip.tests.ctest_indexed_gzip.test_copyable
???
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
x = , memo = {}, _nil = []
def deepcopy(x, memo=None, _nil=[]):
"""Deep copy operation on arbitrary Python objects.
See the module's __doc__ string for more info.
"""
if memo is None:
memo = {}
d = id(x)
y = memo.get(d, _nil)
if y is not _nil:
return y
cls = type(x)
copier = _deepcopy_dispatch.get(cls)
if copier is not None:
y = copier(x, memo)
else:
if issubclass(cls, type):
y = _deepcopy_atomic(x, memo)
else:
copier = getattr(x, "__deepcopy__", None)
if copier is not None:
y = copier(memo)
else:
reductor = dispatch_table.get(cls)
if reductor:
rv = reductor(x)
else:
reductor = getattr(x, "__reduce_ex__", None)
if reductor is not None:
> rv = reductor(4)
E TypeError: cannot pickle 'IndexedGzipFile' instances
/usr/lib/python3.12/copy.py:151: TypeError
- Captured stdout call -
Compressing data with a single call to gzip ... test.gz
Waiting (1.00 minutes)
Waiting (1.00 minutes)
___ test_multiproc_serialise ___
@pytest.mark.slow_test
def test_multiproc_serialise():
> ctest_indexed_gzip.test_multiproc_serialise()
../indexed_gzip/tests/test_indexed_gzip.py:184:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
indexed_gzip/tests/ctest_indexed_gzip.pyx:1152: in
indexed_gzip.tests.ctest_indexed_gzip.test_multiproc_serialise
???
indexed_gzip/tests/ctest_indexed_gzip.pyx:1166: in
indexed_gzip.tests.ctest_indexed_gzip.test_multiproc_serialise
???
/usr/lib/python3.12/multiprocessing/pool.py:367: in map
return self._map_async(func, iterable, mapstar, chunksize).get()
/usr/lib/python3.12/multiprocessing/pool.py:774: in get
raise self._value
/usr/lib/python3.12/multiprocessing/pool.py:540: in _handle_tasks
put(task)
/usr/lib/python3.12/multiprocessing/connection.py:206: in send
self._send_bytes(_ForkingPickler.dumps(obj))
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
cls =
obj = (7, 0, ,
((functools.partial(, ,
250), (0,)),), {})
protocol = None
@classmethod
def dumps(cls, obj, protocol=None):
buf = io.BytesIO()
> cls(buf, protocol).dump(obj)
E TypeError: cannot pickle 'IndexedGzipFile' instances
/usr/lib/python3.12/multiprocessing/reduction.py:51: TypeError
Bug#1070441: cmbc: arm64 FTBFS with glibc 2.38
Source: cbmc Version: 5.95.1-4 Severity: serious Tags: ftbfs Hi Maintainer As can be seen in reproducible builds [1], cbmc FTBFS on arm64 with glibc 2.38. I've copied what I hope is the relevant part of the log below. A bug was filed against glibc [2], but it seems glibc upstream do not consider it a bug in glibc. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/cbmc.html [2] https://sourceware.org/bugzilla/show_bug.cgi?id=30909 [31mTests failed [0m 10 of 1114 tests failed, 60 tests skipped Failed test: Float-div2 CBMC version 5.95.1 (cbmc-5.95.1) 64-bit arm64 linux Parsing main.c file /usr/include/aarch64-linux-gnu/bits/math-vector.h line 30: syntax error before '__f32x4_t' PARSING ERROR EXIT=6 SIGNAL=0 Failed test.desc lines: ^EXIT=0$ [FAILED] ^VERIFICATION SUCCESSFUL$ [FAILED] Failed test: Float-div3 CBMC version 5.95.1 (cbmc-5.95.1) 64-bit arm64 linux Parsing main.c file /usr/include/aarch64-linux-gnu/bits/math-vector.h line 30: syntax error before '__f32x4_t' PARSING ERROR EXIT=6 SIGNAL=0 Failed test.desc lines: ^EXIT=0$ [FAILED] ^VERIFICATION SUCCESSFUL$ [FAILED] Failed test: Float-equality2 CBMC version 5.95.1 (cbmc-5.95.1) 64-bit arm64 linux Parsing main.c file /usr/include/aarch64-linux-gnu/bits/math-vector.h line 30: syntax error before '__f32x4_t' PARSING ERROR EXIT=6 SIGNAL=0 Failed test.desc lines: (Starting CEGAR Loop|VCC\(s\), 0 remaining after simplification$) [FAILED] ^VERIFICATION SUCCESSFUL$ [FAILED] ^EXIT=0$ [FAILED] Failed test: Float-flags-no-simp1 CBMC version 5.95.1 (cbmc-5.95.1) 64-bit arm64 linux Parsing main.c file /usr/include/aarch64-linux-gnu/bits/math-vector.h line 30: syntax error before '__f32x4_t' PARSING ERROR EXIT=6 SIGNAL=0 Failed test.desc lines: ^EXIT=0$ [FAILED] ^VERIFICATION SUCCESSFUL$ [FAILED] Failed test: Float-flags-simp1 CBMC version 5.95.1 (cbmc-5.95.1) 64-bit arm64 linux Parsing main.c file /usr/include/aarch64-linux-gnu/bits/math-vector.h line 30: syntax error before '__f32x4_t' PARSING ERROR EXIT=6 SIGNAL=0 Failed test.desc lines: ^EXIT=0$ [FAILED] ^VERIFICATION SUCCESSFUL$ [FAILED] Failed test: Float-no-simp9 CBMC version 5.95.1 (cbmc-5.95.1) 64-bit arm64 linux Parsing main.c file /usr/include/aarch64-linux-gnu/bits/math-vector.h line 30: syntax error before '__f32x4_t' PARSING ERROR EXIT=6 SIGNAL=0 Failed test.desc lines: ^EXIT=0$ [FAILED] ^VERIFICATION SUCCESSFUL$ [FAILED] Failed test: Float21 CBMC version 5.95.1 (cbmc-5.95.1) 64-bit arm64 linux Parsing main.c file /usr/include/aarch64-linux-gnu/bits/math-vector.h line 30: syntax error before '__f32x4_t' PARSING ERROR EXIT=6 SIGNAL=0 Failed test.desc lines: ^EXIT=0$ [FAILED] ^VERIFICATION SUCCESSFUL$ [FAILED] Failed test: float-nan-check CBMC version 5.95.1 (cbmc-5.95.1) 64-bit arm64 linux Parsing main.c file /usr/include/aarch64-linux-gnu/bits/math-vector.h line 30: syntax error before '__f32x4_t' PARSING ERROR EXIT=6 SIGNAL=0
Bug#1070437: skimage: FTBFS with Python 3.12 as default
Source: skimage Version: 0.22.0-3 Severity: important Tags: ftbfs patch User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer skimage FTBFS with Python 3.12 as the default version (i.e. with python3-defaults/3.12.1-1 from experimental). Please see the patch below to use the vendored distutils in setuptools instead of trying to use the one from stdlib, which is no longer available in Python 3.12 Regards Graham --- a/debian/rules +++ b/debian/rules @@ -25,7 +25,7 @@ export SKIMAGE_TEST_STRICT_WARNINGS := False # Hotfix for #1022461: Force setuptools to be compatible with older version -export SETUPTOOLS_USE_DISTUTILS=stdlib +# export SETUPTOOLS_USE_DISTUTILS=stdlib %: dh $@ --with python3,sphinxdoc --buildsystem pybuild
Bug#1065309: transition: gnat (12 -> 13 + time_t64)
Hi Nicholas On Sat, 4 May 2024 at 12:21, Nicolas Boulenguez wrote: > For some reason, some rebuilds succeeded without a +b1 version. I think if the original uploads FTBFS then they would not have gained a +b1 version. > Their reverse dependencies is dep-waiting on the +b1 version. > Please cancel three dep-wait restrictions. > > gb libgnatcoll-db_23.0.0-6 . armel powerpc . -o > gb libgnatcoll-bindings_24.0.0-2 . armhf . -o I binNMU'd libgnatcoll again on armhf, and libgnatcoll-bindings again on armel, armhf, hppa and powerpc, this should get the +b1 versions aligned and get libgnatcoll-db built. Regards Graham
Bug#1070201: scikit-learn: autopkgtest regression on i386 with NumPy 1.26
Source: scikit-learn
Version: 1.4.1.post1+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
scikit-learn's autopkgtest regresses on i386 when tested with numpy
1.26 [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.debian.net/packages/s/scikit-learn/testing/i386/
1386s === FAILURES
===
35104
1386s __ test_graphviz_toy
___
35105
1386s
35106
1386s def test_graphviz_toy():
35107
1386s # Check correctness of export_graphviz
35108
1386s clf = DecisionTreeClassifier(
35109
1386s max_depth=3, min_samples_split=2, criterion="gini", random_state=2
35110
1386s )
35111
1386s clf.fit(X, y)
35112
1386s
35113
1386s # Test export code
35114
1386s contents1 = export_graphviz(clf, out_file=None)
35115
1386s contents2 = (
35116
1386s "digraph Tree {\n"
35117
1386s 'node [shape=box, fontname="helvetica"] ;\n'
35118
1386s 'edge [fontname="helvetica"] ;\n'
35119
1386s '0 [label="x[0] <= 0.0\\ngini = 0.5\\nsamples = 6\\n'
35120
1386s 'value = [3, 3]"] ;\n'
35121
1386s '1 [label="gini = 0.0\\nsamples = 3\\nvalue = [3, 0]"] ;\n'
35122
1386s "0 -> 1 [labeldistance=2.5, labelangle=45, "
35123
1386s 'headlabel="True"] ;\n'
35124
1386s '2 [label="gini = 0.0\\nsamples = 3\\nvalue = [0, 3]"] ;\n'
35125
1386s "0 -> 2 [labeldistance=2.5, labelangle=-45, "
35126
1386s 'headlabel="False"] ;\n'
35127
1386s "}"
35128
1386s )
35129
1386s
35130
1386s assert contents1 == contents2
35131
1386s
35132
1386s # Test plot_options
35133
1386s contents1 = export_graphviz(
35134
1386s clf,
35135
1386s filled=True,
35136
1386s impurity=False,
35137
1386s proportion=True,
35138
1386s special_characters=True,
35139
1386s rounded=True,
35140
1386s out_file=None,
35141
1386s fontname="sans",
35142
1386s )
35143
1386s contents2 = (
35144
1386s "digraph Tree {\n"
35145
1386s 'node [shape=box, style="filled, rounded", color="black", '
35146
1386s 'fontname="sans"] ;\n'
35147
1386s 'edge [fontname="sans"] ;\n'
35148
1386s "0 [label=0 0.0samples = 100.0%"
35149
1386s 'value = [0.5, 0.5]>, fillcolor="#ff"] ;\n'
35150
1386s "1 [label=value = [1.0, 0.0]>, "
35151
1386s 'fillcolor="#e58139"] ;\n'
35152
1386s "0 -> 1 [labeldistance=2.5, labelangle=45, "
35153
1386s 'headlabel="True"] ;\n'
35154
1386s "2 [label=value = [0.0, 1.0]>, "
35155
1386s 'fillcolor="#399de5"] ;\n'
35156
1386s "0 -> 2 [labeldistance=2.5, labelangle=-45, "
35157
1386s 'headlabel="False"] ;\n'
35158
1386s "}"
35159
1386s )
35160
1386s
35161
1386s assert contents1 == contents2
35162
1386s
35163
1386s # Test max_depth
35164
1386s contents1 = export_graphviz(clf, max_depth=0, class_names=True,
out_file=None)
35165
1386s contents2 = (
35166
1386s "digraph Tree {\n"
35167
1386s 'node [shape=box, fontname="helvetica"] ;\n'
35168
1386s 'edge [fontname="helvetica"] ;\n'
35169
1386s '0 [label="x[0] <= 0.0\\ngini = 0.5\\nsamples = 6\\n'
35170
1386s 'value = [3, 3]\\nclass = y[0]"] ;\n'
35171
1386s '1 [label="(...)"] ;\n'
35172
1386s "0 -> 1 ;\n"
35173
1386s '2 [label="(...)"] ;\n'
35174
1386s "0 -> 2 ;\n"
35175
1386s "}"
35176
1386s )
35177
1386s
35178
1386s assert contents1 == contents2
35179
1386s
35180
1386s # Test max_depth with plot_options
35181
1386s contents1 = export_graphviz(
35182
1386s clf, max_depth=0, filled=True, out_file=None, node_ids=True
35183
1386s )
35184
1386s contents2 = (
35185
1386s "digraph Tree {\n"
35186
1386s 'node [shape=box, style="filled", color="black", '
35187
1386s 'fontname="helvetica"] ;\n'
35188
1386s 'edge [fontname="helvetica"] ;\n'
35189
1386s '0 [label="node #0\\nx[0] <= 0.0\\ngini = 0.5\\n'
35190
1386s 'samples = 6\\nvalue = [3, 3]", fillcolor="#ff"] ;\n'
35191
1386s '1 [label="(...)", fillcolor="#C0C0C0"] ;\n'
35192
1386s "0 -> 1 ;\n"
35193
1386s '2 [label="(...)", fillcolor="#C0C0C0"] ;\n'
35194
1386s "0 -> 2 ;\n"
35195
1386s "}"
35196
1386s )
35197
1386s
35198
1386s assert contents1 == contents2
35199
1386s
35200
1386s # Test multi-output with weighted samples
35201
1386s clf = DecisionTreeClassifier(
35202
1386s max_depth=2, min_samples_split=2, criterion="gini", random_state=2
35203
1386s )
35204
1386s clf = clf.fit(X, y2, sample_weight=w)
35205
1386s
35206
1386s > contents1 = export_graphviz(clf, filled=True, impurity=False,
out_file=None)
35207
1386s
35208
1386s /usr/lib/python3/dist-packages/sklearn/tree/tests/test_export.py:131:
35209
1386s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _
35210
1386s /usr/lib/python3/dist-packages/sklearn/utils/_param_validation.py:213:
in wrapper
35211
1386s return func(*args, **kwargs)
35212
1386s /usr/lib/python3/dist-packages/sklearn/tree/_export.py:906: in
export_graphviz
35213
1386s exporter.export(decision_tree)
35214
1386s /usr/lib/python3/dist-packages/sklearn/tree/_export.py:466: in export
35215
1386s self.recurse(decision_tree.tree_, 0,
Bug#1065309: transition: gnat (12 -> 13 + time_t64)
Hi Nicholas I think the builds are on track, except for: libtemplates-parser FTBFS on arch:all [1] gprbuild FTBFS on arch:any [2] libgnatcoll, libgnatcoll-bindings and libgnatcoll-db are blocked by the builds of gprbuild Regards Graham [1] https://buildd.debian.org/status/package.php?p=libtemplates-parser=sid [2] https://buildd.debian.org/status/package.php?p=gprbuild=sid
Bug#1065309: transition: gnat (12 -> 13 + time_t64)
Hi Nicholas On Tue, 30 Apr 2024 at 12:33, Nicolas Boulenguez wrote: > The time_t64 transition has triggered #1067453 in the Ada compiler, > which is now fixed by gcc-13/13.2.0-24. > > The patch modifies the sources of the Ada standard library, so most > Ada packages need a rebuild in order to update their dependencies > (gnat-13 Provides: gnat-13-HASH > each Ada library Provides: libFOO-dev-HASH > and each consumer Depends: gnat-13-HASH, libFOO-HASH). > > Please schedule the following rebuilds. > > nmu adacgi_1.6-34 . ANY . -m 'Rebuild with #1067453 fixed in > gnat. Closes: #1067070.' > dw adacgi_1.6-34 . ANY . -m 'gnat-13 (>= 13.2.0-24)' > nmu adasockets_1.14-1 . ANY . -m 'Rebuild with #1067453 fixed in > gnat.' > dw adasockets_1.14-1 . ANY . -m 'gnat-13 (>= 13.2.0-24)' > nmu ahven_2.8.9 . ANY . -m 'Rebuild with #1067453 fixed in > gnat. Closes: #1067224, #1069469.' > dw ahven_2.8.9 . ANY . -m 'gnat-13 (>= 13.2.0-24)' > nmu libaunit_24.0.0-2 . ANY . -m 'Rebuild with #1067453 fixed in > gnat. Closes: #1067071.' > dw libaunit_24.0.0-2 . ANY . -m 'gnat-13 (>= 13.2.0-24)' > nmu libgmpada_1.6-2 . ANY . -m 'Rebuild with #1067453 fixed in > gnat.' > dw libgmpada_1.6-2 . ANY . -m 'gnat-13 (>= 13.2.0-24)' > nmu libncursesada_6.3.20211021-11 . ANY . -m 'Rebuild with #1067453 fixed in > gnat. Closes: #1067073.' > dw libncursesada_6.3.20211021-11 . ANY . -m 'gnat-13 (>= 13.2.0-24)' > nmu libtexttools_2.1.0-28 . ANY . -m 'Rebuild with #1067453 fixed in > gnat. Closes: #1069476.' > dw libtexttools_2.1.0-28 . ANY . -m 'gnat-13 (>= 13.2.0-24)' > nmu libxmlada_24.0.0-2. ANY . -m 'Rebuild with #1067453 fixed in > gnat' > dw libxmlada_24.0.0-2. ANY . -m 'gnat-13 (>= 13.2.0-24)' > nmu libxmlezout_1.06.2-14 . ANY . -m 'Rebuild with #1067453 fixed in > gnat. Closes: #1067220.' > dw libxmlezout_1.06.2-14 . ANY . -m 'gnat-13 (>= 13.2.0-24)' > > nmu liblog4ada_1.3.1.b6dafb49-13 . ANY . -m 'Rebuild with #1067453 fixed in > gnat. Closes: #1067074.' > dw liblog4ada_1.3.1.b6dafb49-13 . ANY . -m 'libxmezout-dev (>= > 1.06.2-14+b1)' > > nmu anet_0.5.0-3 . ANY . -m 'Rebuild with #1067453 fixed in > gnat. Closes: #1067353.' > dw anet_0.5.0-3 . ANY . -m 'libahven-dev (>= 2.8.9+b1)' > nmu dbusada_0.6.2-6 . ANY . -m 'Rebuild with #1067453 fixed in > gnat. Closes: #1069421.' > dw dbusada_0.6-2-6 . ANY . -m 'libahven-dev (>= 2.8.9+b1)' > nmu libalog_0.6.2-5 . ANY . -m 'Rebuild with #1067453 fixed in > gnat. Closes: #1069454.' > dw libalog_0.6.2-5 . ANY . -m 'libahven-dev (>= 2.8.9+b1)' > nmu pcscada_0.7.7-6 . ANY . -m 'Rebuild with #1067453 fixed in > gnat. Closes: #1069468.' > dw pcscada_0.7.7-6 . ANY . -m 'libahven-dev (>= 2.8.9+b1)' > > nmu libtemplates-parser_24.0.0-2 . ANY . -m 'Rebuild with #1067453 fixed in > gnat.' > dw libtemplates-parser_24.0.0-2 . ANY . -m 'libxmlada-unicode-dev (>= > 24.0.0-2+b1)' > nmu gprbuild_2024.1.20231009-4. ANY . -m 'Rebuild with #1067453 fixed in > gnat. Closes: #1069467.' > dw gprbuild_2024.1.20231009-4. ANY . -m 'libxmlada-unicode-dev (>= > 24.0.0-2+b1)' > > nmu libgnatcoll_24.1.20230921-4 . ANY . -m 'Rebuild with #1067453 fixed in > gnat.' > dw libgnatcoll_24.1.20230921-4 . ANY . -m 'libgnatprj-dev (>= > 2024.1.20231009-4+b1)' > > nmu libgnatcoll-bindings_24.0.0-2 . ANY . -m 'Rebuild with #1067453 fixed in > gnat.' > dw libgnatcoll-bindings_24.0.0-2 . ANY . -m 'libgnatcoll-dev (>= > 24.1.20230921-4+b1)' > > nmu libgnatcoll-db_23.0.0-6 . ANY . -m 'Rebuild with #1067453 fixed in > gnat.' > dw libgnatcoll-db_23.0.0-6 . ANY . -m 'libgnatcoll-iconv-dev (>= > 24.0.0-2+b1)' Scheduled, thanks, with a couple of fixed typos in versions; ahven_2.8.9 -> 2.8-9 and dbusada_0.6-2-6 -< 0.6.2-6. I'll check on the buildst later to see if any additional binNMUs are required to get the +b versions aligned. Regards Graham
Bug#1069051: r-cran-spatstat.model: autopkgtest regression in testing
Source: r-cran-spatstat.model Version: 3.2-8-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2023-12-01, r-cran-spatstat.model's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/r/r-cran-spatstat.model/testing/amd64/ 104s Error in check.nvector(weights, nX, vname = "weights") : 104s Some values of weights are NA or NaN 104s Calls: local ... diagnose.ppm.engine -> density.ppp -> pointweights -> check.nvector 104s In addition: Warning messages: 104s 1: Values of the covariate ‘cv’ were NA or undefined at 96% (1774 out of 1845) of the quadrature points. Occurred while executing: ppm.ppp(Q = Y, trend = ~cv + I(cv^2), data = list(list(c(1, 1.91953576453823, 104s 2: Some infinite, NA or NaN increments were removed 104s 3: Numerical underflow detected: sigma is probably too small 104s Execution halted
Bug#1057204: RM: r-bioc-rhdf5filters [s390x] -- ROM; Build-Depends missing on s390x
Hi Andreas It looks like the issue with r-bioc-rhdf5filters was fxied in 1.14.1+dfsg-2. Is removal still required? Regards Graham
Bug#1066310: dx: FTBFS: _compparse.c:51:17: error: implicit declaration of function ‘_dxfcclex’ [-Werror=implicit-function-declaration]
Hi Bo > I have attached one debdiff and it can be built with it. So could you > upload it with it? The attached patch just seems to be papering over the problem, so I would rather not. Regards Graham
Bug#1067233: python-pomegranate: autopkgtest regression with NumPy 1.26
Control: tags -1 + patch Hi Maintainer The attached patch fixes the test failures for me. I noticed in this package's changelog that its only purpose is to work with cnvkit. I have not tested whether cnvkit still functions with this patch in place. Regards Graham Description: Only compare init as a string after determining its type Avoids the following with error NumPy 1.26: ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all() Bug-Debian: https://bugs.debian.org/1067233 Author: Graham Inggs Last-Update: 2024-04-06 --- a/pomegranate/kmeans.pyx +++ b/pomegranate/kmeans.pyx @@ -229,10 +229,6 @@ def __init__(self, k, init='kmeans++', n_init=10): self.k = k - if init != 'first-k': - self.n_init = n_init - else: - self.n_init = 1 self.centroid_norms = calloc(self.k, sizeof(double)) if isinstance(init, (list, numpy.ndarray)): @@ -246,8 +242,14 @@ self.centroid_norms[i] = self.centroids[i].dot(self.centroids[i]) self.init = 'fixed' + self.n_init = n_init elif isinstance(init, str): self.init = init + if init != 'first-k': +self.n_init = n_init + else: +self.n_init = 1 + def __dealloc__(self): free(self.centroid_norms)
Bug#1067234: symfit: autopkgtest regression with NumPy 1.26
Control: tags -1 + patch
Hi Maintainer
While asserting that no warnings are raised is a useful test for the
upstream developers, I don't think it makes sense for downstreams.
I propose to disable the assertion as follows:
--- a/tests/test_minimizers.py
+++ b/tests/test_minimizers.py
@@ -117,7 +117,7 @@
# Should no longer raise warnings, because internally we practice
# what we preach.
fit_custom = BFGS(chi_squared, [a, b])
-assert len(recwarn) == 0
+#assert len(recwarn) == 0
fit_custom_result = fit_custom.execute()
Please let me know if you are happy with a team upload and I will proceed.
As a bonus, I attach a patch that fixes several SyntaxWarnings that
occur with Python 3.12.
Regards
Graham
Description: Fix several SyntaxWarnings
Use raw strings to avoid invalid escape sequence
Author: Graham Inggs
Last-Update: 2024-04-06
--- a/symfit/core/operators.py
+++ b/symfit/core/operators.py
@@ -45,7 +45,7 @@
# return orig_ne(self.__class__, other)
def call(self, *values, **named_values):
-"""
+r"""
Call an expression to evaluate it at the given point.
Future improvements: I would like if func and signature could be buffered after the
--- a/symfit/core/support.py
+++ b/symfit/core/support.py
@@ -293,7 +293,7 @@
return jac
def key2str(target):
-"""
+r"""
In ``symfit`` there are many dicts with symbol: value pairs.
These can not be used immediately as \*\*kwargs, even though this would make
a lot of sense from the context.
@@ -321,4 +321,4 @@
base_str += 'd{}{}'.format(var, count if count > 1 else '')
return base_str
-sympy.Derivative.name = property(name)
\ No newline at end of file
+sympy.Derivative.name = property(name)
--- a/symfit/core/fit.py
+++ b/symfit/core/fit.py
@@ -29,7 +29,7 @@
from the model.
"""
def __init__(self, model, *ordered_data, absolute_sigma=None, **named_data):
-"""
+r"""
:param model: (dict of) sympy expression or ``Model`` object.
:param bool absolute_sigma: True by default. If the sigma is only used
for relative weights in your problem, you could consider setting it to
--- a/symfit/core/minimizers.py
+++ b/symfit/core/minimizers.py
@@ -208,7 +208,7 @@
:class:`~symfit.core.minimizers.DifferentialEvolution`.
"""
def __init__(self, *args, minimizers=None, **kwargs):
-'''
+r'''
:param minimizers: a :class:`~collections.abc.Sequence` of
:class:`~symfit.core.minimizers.BaseMinimizer` objects, which need
to be run in order.
@@ -324,7 +324,7 @@
def execute(self, bounds=None, jacobian=None, hessian=None,
constraints=None, *, tol=1e-9, **minimize_options):
-"""
+r"""
Calls the wrapped algorithm.
:param bounds: The bounds for the parameters. Usually filled by
@@ -790,7 +790,7 @@
return lbounds, ubounds
def execute(self, jacobian=None, method='trf', **minpack_options):
-"""
+r"""
:param \*\*minpack_options: Any named arguments to be passed to
:func:`scipy.optimize.least_squares`
"""
--- a/symfit/core/fit_results.py
+++ b/symfit/core/fit_results.py
@@ -26,7 +26,7 @@
:class:`~symfit.core.models.Model`'s.
"""
def __init__(self, model, popt, covariance_matrix, minimizer, objective, message, *, constraints=None, **minimizer_output):
-"""
+r"""
:param model: :class:`~symfit.core.models.Model` that was fit to.
:param popt: best fit parameters, same ordering as in model.params.
:param covariance_matrix: covariance matrix.
@@ -276,4 +276,4 @@
f_is = [f_is[var] for var in model.dependent_vars]
SS_res = np.sum([np.sum((y_i - f_i)**2) for y_i, f_i in zip(y_is, f_is) if y_i is not None])
SS_tot = np.sum([np.sum((y_i - y_bar)**2) for y_i, y_bar in zip(y_is, y_bars) if y_i is not None])
-return 1 - SS_res/SS_tot
\ No newline at end of file
+return 1 - SS_res/SS_tot
--- a/symfit/core/objectives.py
+++ b/symfit/core/objectives.py
@@ -386,7 +386,7 @@
class HessianObjectiveJacApprox(HessianObjective):
-"""
+r"""
This object should only be used as a Mixin for covariance matrix estimation.
Since the covariance matrix for the least-squares method is proportional to
the Hessian of :math:`S`, this function attempts to return the Hessian
@@ -552,4 +552,4 @@
)
return np.array(evaluated_hess[0])
else:
-return None
\ No newline at end of file
+return None
Bug#1068240: nauty: autopkgtest regression in testing
Source: nauty Version: 2.8.8+ds-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2024-01-23, nauty's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/n/nauty/testing/amd64/ 60s The following packages have unmet dependencies: 60s autopkgtest-satdep : Depends: libnauty2-dev but it is not installable 60s E: Unable to correct problems, you have held broken packages. 60s autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs 60s Reading package lists... 60s Building dependency tree... 60s Reading state information... 60s Package libnauty2-dev is not available, but is referred to by another package. 60s This may mean that the package is missing, has been obsoleted, or 60s is only available from another source 60s 60s E: Package 'libnauty2-dev' has no installation candidate 60s build-examples FAIL badpkg 60s blame: nauty 60s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
Bug#1068104: pandas: FTBFS on 32-bit architectures with -D_TIME_BITS=64
Source: pandas Version: 2.1.4+dfsg-6 Severity: serious Tags: ftbfs patch Hi Maintainer pandas FTBFS on 32-bit architectures with -D_TIME_BITS=64 (e.g. armel and armhf), due to tests expected to fail, now passing. I've copied what I hope are the relevant parts of the log below. The following is my first attempt at a patch, which would pass on armel and armhf, but fail on i386 and hurd-i386, which are not built with -D_TIME_BITS=64. --- a/pandas/tests/indexes/datetimes/test_ops.py +++ b/pandas/tests/indexes/datetimes/test_ops.py @@ -33,7 +33,7 @@ ) def test_resolution(self, request, tz_naive_fixture, freq, expected): tz = tz_naive_fixture -if freq == "A" and not IS64 and isinstance(tz, tzlocal): +if freq == "A" and isinstance(tz, tzlocal): request.node.add_marker( pytest.mark.xfail(reason="OverflowError inside tzlocal past 2038") ) --- a/pandas/tests/tseries/offsets/test_common.py +++ b/pandas/tests/tseries/offsets/test_common.py @@ -139,7 +139,7 @@ if tz is not None: assert t.tzinfo is not None -if isinstance(tz, tzlocal) and not IS64 and _offset is not DateOffset: +if isinstance(tz, tzlocal) and _offset is not DateOffset: # If we hit OutOfBoundsDatetime on non-64 bit machines # we'll drop out of the try clause before the next test request.node.add_marker( The following is my second attempt at a patch, which does not fail if the expected test failures succeed. --- a/pandas/tests/indexes/datetimes/test_ops.py +++ b/pandas/tests/indexes/datetimes/test_ops.py @@ -35,7 +35,7 @@ tz = tz_naive_fixture if freq == "A" and not IS64 and isinstance(tz, tzlocal): request.node.add_marker( -pytest.mark.xfail(reason="OverflowError inside tzlocal past 2038") +pytest.mark.xfail(reason="OverflowError inside tzlocal past 2038",strict=False) ) idx = date_range(start="2013-04-01", periods=30, freq=freq, tz=tz) --- a/pandas/tests/tseries/offsets/test_common.py +++ b/pandas/tests/tseries/offsets/test_common.py @@ -143,7 +143,7 @@ # If we hit OutOfBoundsDatetime on non-64 bit machines # we'll drop out of the try clause before the next test request.node.add_marker( -pytest.mark.xfail(reason="OverflowError inside tzlocal past 2038") +pytest.mark.xfail(reason="OverflowError inside tzlocal past 2038", strict=False) ) elif ( isinstance(tz, tzlocal) Regards Graham [1] https://buildd.debian.org/status/logs.php?pkg=pandas=armhf [2] https://buildd.debian.org/status/logs.php?pkg=pandas=armel === short test summary info FAILED pandas/tests/indexes/datetimes/test_ops.py::TestDatetimeIndexOps::test_resolution[tzlocal()-A-day] = 1 failed, 15623 passed, 383 skipped, 5 deselected, 46 xfailed, 4 xpassed in 47.98s = rdjoqkol test state = false === short test summary info FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-BusinessDay] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-BusinessHour] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-BusinessMonthEnd] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-BusinessMonthBegin] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-BQuarterEnd] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-BQuarterBegin] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-CustomBusinessDay] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-CustomBusinessHour] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-CustomBusinessMonthEnd] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-CustomBusinessMonthBegin] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-MonthEnd] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-MonthBegin] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-SemiMonthBegin] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-SemiMonthEnd] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-QuarterEnd] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-LastWeekOfMonth] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-WeekOfMonth] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-Week]
Bug#1067598: wfuzz: FTBFS with Python 3.12 as default
Control: tags -1 + patch
The attached patch avoids the use of distutils and imp which are no
longer available in Python 3.12. I believe this will close this bug
(#1067598) as well as #1066009 [1].
I did not test the package exhaustively, but was able to get similar
output to that described in #1015016 [2], when running the following
command with only Python 3.12 installed:
wfuzz --dry-run -w /usr/share/wfuzz/wordlist/general/test.txt -u
http://127.0.0.1/FUZZ
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066009
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015016
Description: Avoid the use of distutils and imp
No longer available in Python 3.12
Bug-Debian: https://bugs.debian.org/1066009
Bug-Debian: https://bugs.debian.org/1067598
Author: Graham Inggs
Last-Update: 2024-03-25
--- a/src/wfuzz/externals/moduleman/loader.py
+++ b/src/wfuzz/externals/moduleman/loader.py
@@ -1,6 +1,6 @@
import inspect
import logging
-import imp
+import importlib
import os.path
@@ -52,14 +52,13 @@
"""
self.__logger.debug("__load_py_from_file. START, file=%s" % (filename,))
-dirname, filename = os.path.split(filename)
-fn = os.path.splitext(filename)[0]
-exten_file = None
+fn = os.path.splitext(os.path.split(filename)[1])[0]
module = None
try:
-exten_file, filename, description = imp.find_module(fn, [dirname])
-module = imp.load_module(fn, exten_file, filename, description)
+spec = importlib.util.spec_from_file_location(fn, filename)
+module = importlib.util.module_from_spec(spec)
+spec.loader.exec_module(module)
except ImportError as msg:
self.__logger.critical(
"__load_py_from_file. Filename: %s Exception, msg=%s" % (filename, msg)
@@ -73,9 +72,6 @@
)
# raise msg
pass
-finally:
-if exten_file:
-exten_file.close()
if module is None:
return
--- a/src/wfuzz/plugin_api/base.py
+++ b/src/wfuzz/plugin_api/base.py
@@ -10,11 +10,24 @@
import sys
import os
-from distutils import util
# python 2 and 3: iterator
from builtins import object
+def strtobool(val):
+"""Convert a string representation of truth to true (1) or false (0).
+
+True values are 'y', 'yes', 't', 'true', 'on', and '1'; false values
+are 'n', 'no', 'f', 'false', 'off', and '0'. Raises ValueError if
+'val' is anything else.
+"""
+val = val.lower()
+if val in ('y', 'yes', 't', 'true', 'on', '1'):
+return 1
+elif val in ('n', 'no', 'f', 'false', 'off', '0'):
+return 0
+else:
+raise ValueError("invalid truth value {!r}".format(val))
# Util methods for accessing search results
class BasePlugin:
@@ -74,7 +87,7 @@
)
def _bool(self, value):
-return bool(util.strtobool(value))
+return bool(strtobool(value))
class BasePrinter:
Bug#1067598: wfuzz: FTBFS with Python 3.12 as default
Source: wfuzz
Version: 3.1.0-4
Severity: important
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
Hi Maintainer
wfuzz FTBFS with Python 3.12 as the default version (i.e. with
python3-defaults/3.12.1-1 from experimental). I've copied what I hope
is the relevant part of the log below.
Regards
Graham
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:305: cd
/<>/.pybuild/cpython3_3.12_wfuzz/build; python3.12 -m
unittest discover -v
wfuzz (unittest.loader._FailedTest.wfuzz) ... ERROR
==
ERROR: wfuzz (unittest.loader._FailedTest.wfuzz)
--
ImportError: Failed to import test module: wfuzz
Traceback (most recent call last):
File "/usr/lib/python3.12/unittest/loader.py", line 427, in _find_test_path
package = self._get_module_from_name(name)
File "/usr/lib/python3.12/unittest/loader.py", line 337, in
_get_module_from_name
__import__(name)
File "/<>/.pybuild/cpython3_3.12_wfuzz/build/wfuzz/__init__.py",
line 55, in
from .options import FuzzSession
File "/<>/.pybuild/cpython3_3.12_wfuzz/build/wfuzz/options.py",
line 6, in
from .facade import (
File "/<>/.pybuild/cpython3_3.12_wfuzz/build/wfuzz/facade.py",
line 5, in
from .externals.moduleman.loader import DirLoader
File
"/<>/.pybuild/cpython3_3.12_wfuzz/build/wfuzz/externals/moduleman/loader.py",
line 3, in
import imp
ModuleNotFoundError: No module named 'imp'
--
Ran 1 test in 0.000s
FAILED (errors=1)
E: pybuild pybuild:391: test: plugin distutils failed with: exit
code=1: cd /<>/.pybuild/cpython3_3.12_wfuzz/build;
python3.12 -m unittest discover -v
dh_auto_test: error: pybuild --test -i python{version} -p 3.12
returned exit code 13
Bug#1065961: [Debian-med-packaging] Bug#1065961: sra-sdk: Please drop dependencies on python3-distutils
Hi Aaron On Thu, 14 Mar 2024 at 02:03, Aaron M. Ucko wrote: > I hear you, but can't readily determine whether any additional changes > would be in order until dh-python drops or downgrades its distutils > dependency, which I called out just now: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066833 For what it's worth, sra-sdk was able to build in Ubuntu, where python3-distutils is already gone from dh-python, after only dropping the build-dependency in sra-sdk. Even if this were not the case, I'd say it is safe to drop the build-dependency now, because if additional changes were required, it would be detected in the test rebuild following the Python 3.12 transition. Regards Graham
Bug#1066978: mathgl: new autopkgtest fails on s390x
Source: mathgl Version: 8.0.1-7 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer It seems mathgl 8.0.1-7 introduced a new autopkgtest. That's great! However, it fails on s390x [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/m/mathgl/testing/s390x/ 162s autopkgtest [15:25:45]: test command1: [--- 166s terminate called after throwing an instance of 'std::bad_array_new_length' 166s what(): std::bad_array_new_length 166s Aborted 166s autopkgtest [15:25:49]: test command1: ---]
Bug#1065309: transition: gnat (12 -> 13 + time_t64)
Control: tags -1 confirmed Hi Matthias, Nicolas On Sat, 2 Mar 2024 at 12:39, Matthias Klose wrote: > when preparing GCC packages for time_t64, I noticed that we'll have an > ABI change for libgnat as well. Instead of doing a gnat 12 -> 12+t64 > transition, let's do a gnat 12 -> 13+t64 transition instead. According > to Nicolas, packages are already prepared in experimental. On Wed, 13 Mar 2024 at 19:51, wrote: > I agree with Matthias that we should instead start the gcc-13 transition > in unstable. All packages are ready in experimental, with all library > packages already renamed through NEW. But unfortunately also with > intrusive unrelated changes, for example new upstream versions and a new > Ada workflow removing the version from -dev package names. It makes sense to do it in one go, please go ahead. Regards Graham
Bug#1065309: transition: gnat 12 -> 13 + time_t64
Hi Nicolas, Matthias On Sun, 3 Mar 2024 at 16:18, Nicolas Boulenguez wrote: > Ben file: > > title = "gnat-13"; > is_affected = .depends ~ > "libgnat-8/libgnat-9/libgnat-10/libgnat-11/libgnat-12" | .depends ~ > "libgnat-13"; > is_good = .depends ~ "libgnat-13"; > is_bad = .depends ~ "libgnat-8/libgnat-9/libgnat-10/libgnat-11/libgnat-12"; ben did not like the syntax, but I think I understood your intention and set up a tracker [1]. After seeing the output, I tried to simplify it, and assumed that gcc need not be included. I set up a second version of the tracker [2]. Please let me know if these need further refinement. If not, let me know which tracker you prefer to keep. Regards Graham [1] https://release.debian.org/transitions/html/gnat-13.html [2] https://release.debian.org/transitions/html/gnat-13-v2.html
Bug#1066498: dh-make-perl: autopkgtest regression due to time_t transition
Source: dh-make-perl
Version: 0.123
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
dh-make-perl's autopkgtest regress when tested with perl/5.38.2-3.2
[1]. I've copied what I hope is the relevant part of the log below.
>From what I can see on the excuses page for perl [2], dh-make-perl's
autopkgtests are the only ones failing on all architectures, besides
perl's own. Do these test cases need updating to handle the 't64'?
Regards
Graham
[1] https://ci.debian.net/packages/d/dh-make-perl/testing/amd64/
[2] https://qa.debian.org/excuses.php?package=perl
80s t/DpkgLists.t ...
80s 1..7
80s ok 1 - use Debian::DpkgLists;
80s # Perl API is 5.38
80s ok 2 - /usr/bin/perl is in perl-base
80s ok 3 - partial /bin/perl is in perl-base
80s ok 4 - qr{/bin/perl$} is in perl-base
80s not ok 5 - Errno is in libperl5.38 or perl-base (or only perl-base
for perl < 5.22)
80s
80s # Failed test 'Errno is in libperl5.38 or perl-base (or only
perl-base for perl < 5.22)'
80s # at t/DpkgLists.t line 33.
80s # Structures begin differing at:
80s # $got->[0] = 'libperl5.38t64'
80s # $expected->[0] = 'libperl5.38'
80s not ok 6 - IO::Socket::UNIX is in libperl5.38 or perl-base (or
only perl-base for perl < 5.22)
80s
80s # Failed test 'IO::Socket::UNIX is in libperl5.38 or perl-base (or
only perl-base for perl < 5.22)'
80s # at t/DpkgLists.t line 39.
80s # Structures begin differing at:
80s # $got->[0] = 'libperl5.38t64'
80s # $expected->[0] = 'libperl5.38'
80s ok 7 - utf8 is in perl-base or perl-modules-5.38 (or only
perl-base for perl < 5.22)
80s # Looks like you failed 2 tests of 7.
80s Dubious, test returned 2 (wstat 512, 0x200)
80s Failed 2/7 subtests
Bug#1066003: libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed.
This was solved in Ubuntu by a no-change rebuild of db5.3. A binNMU was scheduled for db5.3. However, the build logs for 5.3.28+dfsg2-5+b1, at least on armel [1] and armhf [2], still show: checking for 64-bit integral type support for sequences... no checking for growing a file under an mmap region... no Ubuntu is further along in the time_t transition, so further investigation is needed as to which package causes the change in buld behaviour of db5.3. [1] https://buildd.debian.org/status/logs.php?pkg=db5.3=armel [2] https://buildd.debian.org/status/logs.php?pkg=db5.3=armhf
Bug#1066003: libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed.
I think the actual error is: # : BDB4015 library build did not include support for sequences # Failed test (t/sequence.t at line 33) # The object isn't defined Can't call method "set_cachesize" on an undefined value at t/sequence.t line 35. # Looks like you planned 13 tests but only ran 3. # Looks like your test died just after 3. t/sequence.t ... 1..13 ok 1 ok 2 - The object isa BerkeleyDB::Env not ok 3 - The object isa BerkeleyDB::Sequence Dubious, test returned 255 (wstat 65280, 0xff00) Failed 11/13 subtests Looking at recent build logs for db5.3 on armhf [1], the build log of 5.3.28+dfsg2-4.1 shows: checking for 64-bit integral type support for sequences... no checking for growing a file under an mmap region... no Whereas the build logs of 5.3.28+dfsg2-4.1~exp1 and older show: checking for 64-bit integral type support for sequences... yes checking for growing a file under an mmap region... yes Regards Graham [1] https://buildd.debian.org/status/logs.php?pkg=db5.3=armhf
Bug#1066012: zfs-dkms: Please drop dependencies on python3-distutils
Source: zfs-dkms Version: 2.2.3-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1066011: whipper: Please drop dependencies on python3-distutils
Source: whipper Version: 0.10.0-2 Severity: important Tags: trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1066009: wfuzz: Please drop dependencies on python3-distutils
Source: wfuzz Version: 3.1.0-4 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1066008: weresync: Please drop dependencies on python3-distutils
Source: weresync Version: 1.1.5-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1066006: waypipe: Please drop dependencies on python3-distutils
Source: waypipe Version: 0.8.6-1 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1066004: virulencefinder: Please drop dependencies on python3-distutils
Source: virulencefinder Version: 2.0.5-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1066002: virt-manager: Please drop dependencies on python3-distutils
Source: virt-manager Version: 1:4.1.0-3 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1066000: viagee: Please drop dependencies on python3-distutils
Source: viagee Version: 3.7.1-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065998: versiontools: Please drop dependencies on python3-distutils
Source: versiontools Version: 1.9.1-4 Severity: important Tags: ftbfs trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065996: uwsgi: Please drop dependencies on python3-distutils
Source: uwsgi Version: 2.0.24-2 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065994: ust: Please drop dependencies on python3-distutils
Source: ust Version: 2.13.7-1 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065992: ufw: Please drop dependencies on python3-distutils
Source: ufw Version: 0.36.2-5 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065991: udisks2: Please drop dependencies on python3-distutils
Source: udisks2 Version: 2.10.1-5 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065990: udiskie: Please drop dependencies on python3-distutils
Source: udiskie Version: 2.5.2-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065989: tulip: Please drop dependencies on python3-distutils
Source: tulip Version: 5.4.0+dfsg-3 Severity: important Tags: ftbfs trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065988: trydiffoscope: Please drop dependencies on python3-distutils
Source: trydiffoscope Version: 67.0.6 Severity: important Tags: ftbfs trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065987: toil: Please drop dependencies on python3-distutils
Source: toil Version: 6.1.0-2 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065984: thefuck: Please drop dependencies on python3-distutils
Source: thefuck Version: 3.29-0.3 Severity: important Tags: trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065983: systemfixtures: Please drop dependencies on python3-distutils
Source: systemfixtures Version: 0.6.4-2 Severity: important Tags: trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065970: system-config-printer: Please drop dependencies on python3-distutils
Source: system-config-printer Version: 1.5.18-1 Severity: important Tags: ftbfs trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065968: sympy: Please drop dependencies on python3-distutils
Source: sympy Version: 1.12-7 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065967: sunpy: Please drop dependencies on python3-distutils
Source: sunpy Version: 5.1.1-1 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065965: streamtuner2: Please drop dependencies on python3-distutils
Source: streamtuner2 Version: 2.2.2+dfsg-2 Severity: important Tags: trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065964: stegcracker: Please drop dependencies on python3-distutils
Source: stegcracker Version: 2.1.0-3 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065962: sshuttle: Please drop dependencies on python3-distutils
Source: sshuttle Version: 1.1.2-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065961: sra-sdk: Please drop dependencies on python3-distutils
Source: sra-sdk Version: 3.0.3+dfsg-6 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065960: spopt: Please drop dependencies on python3-distutils
Source: spopt Version: 0.5.0-4 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065959: sphinx: Please drop dependencies on python3-distutils
Source: sphinx Version: 7.2.6-4 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065958: soapysdr: Please drop dependencies on python3-distutils
Source: soapysdr Version: 0.8.1-4 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065957: sndobj: Please drop dependencies on python3-distutils
Source: sndobj Version: 2.6.7+ds1-3 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065955: slepc4py: Please drop dependencies on python3-distutils
Source: slepc4py Version: 3.19.2-3 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065953: sagemath: Please drop dependencies on python3-distutils
Source: sagemath Version: 9.5-6 Severity: important Tags: ftbfs trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065952: s-tui: Please drop dependencies on python3-distutils
Source: s-tui Version: 1.1.6-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065950: rss2email: Please drop dependencies on python3-distutils
Source: rss2email Version: 1:3.13.1-3 Severity: important Tags: ftbfs trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065948: rnp: Please drop dependencies on python3-distutils
Source: rnp Version: 0.17.0-3 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065945: q2-emperor: Please drop dependencies on python3-distutils
Source: q2-emperor Version: 2023.9.0-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065946: q2-sample-classifier: Please drop dependencies on python3-distutils
Source: q2-sample-classifier Version: 2023.9.0-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065943: pytorch-cuda: Please drop dependencies on python3-distutils
Source: pytorch-cuda Version: 2.1.2+dfsg-3 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065941: pytorch: Please drop dependencies on python3-distutils
Source: pytorch Version: 2.1.2+dfsg-2 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065939: python-thinc: Please drop dependencies on python3-distutils
Source: python-thinc Version: 8.2.2-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
