Hi, The next step for the riscv64 architecture is to get a testing suite. The testing migration script only allows packages that have been built on an official buildds to migrate to testing. Consequently, following the bootstrapping process and once the buildds got reinstalled as official ones (although physically they are still the same machines), we had to rebuild the whole archive. The rebuild took some time, as it got entangled in the time_t transition, and the last rebuilds got scheduled a few days ago. At this stage 58 packages in unstable have not been built on an official buildd. You will find below a status with an explanation of the failure (apologies for the formatting with wide lines). Note that a live version of the list (without explanations) exists [1]. Nevertheless, given the low number of packages that still needs to get rebuilt, and after discussion with the releas team, I will request ftpmasters to add a testing suite for riscv64. Regards Aurelien * Packages in testing which can not be built on riscv64 cfengine3_3.21.0-3 | to be investigated gcc-doc-defaults_5:27 | can't be binNMUed golang-k8s-kube-openapi_0.0~git20211014.b3fe75c-2 | riscv64 FTBFS: #1064362 libsass-python_0.22.0-1 | general FTBFS: #1058362 opam_2.1.5-1 | general FTBFS: #1054822 pymupdf_1.23.7+ds1-1 | general FTBFS: #1064772 rnp_0.17.0-3 | to be investigated ruby-redcloth_4.3.2-4 | to be investigated rust-shared-library_0.1.9-2 | to be investigated sccache_0.5.4-12 | to be investigated, seems to be linked with the switch of rustc from llvm14 to llvm15 strace_6.5-0.1 | general FTBFS: #1060789 We should prioritize our efforts on the above packages, especially the ones that are low in the stack. For one without patches, that means investigating the issue and providing patches. For the ones with patches available for some time, that means scheduling an NMU. * Packages that are not in testing ap-utils_1.5-5 | not in testing, general FTBFS: #1057542 bind-dyndb-ldap_11.10-6 | not in testing, general FTBFS: #1064294 clazy_1.11-4 | not in testing, general FTBFS: #1051858 coz-profiler_0.2.2-2 | not in testing, general FTBFS: #1066941 d1x-rebirth_0.58.1-1.2 | not in testing, general FTBFS: #1057551 d2x-rebirth_0.58.1-1.3 | not in testing, general FTBFS: #1057552 dogecoin_1.14.6-4 | not in testing, general FTBFS: #1059133 dradio_3.8-2.1 | not in testing, general FTBFS: #1057554 gamescope_3.12.5-1 | not in testing, general FTBFS: #1058493 glosstex_0.4.dfsg.1-4 | not in testing, general FTBFS: #1052914 haskell-hsyaml-aeson_0.2.0.1-1 | not in testing, unsatisfiable build-dependency: #1054961 haskell-hsyaml_0.2.1.1-2 | not in testing, general FTBFS: #1054863 haskell-ircbot_0.6.6.1-1 | not in testing, unsatisfiable build-dependency: #1054947 haskell-raaz_0.2.1-2.1 | not in testing, unsatisfiable build-dependency: #1054978 haskell-reform-hsp_0.2.7.2-2 | not in testing, general FTBFS: #1054865 haskell-tidal_1.7.10-1 | not in testing, general FTBFS: #1054931 haskell-userid_0.1.3.7-1 | not in testing, unsatisfiable build-dependency: #1054977 ibus-anthy_1.5.15-1 | not in testing, general FTBFS: #1060953 intel-hdcp_20.3.0-1 | not in testing, general FTBFS: #1052643 libamplsolver_0~20190702-2 | not in testing, general FTBFS: #1040396 libkkc_0.3.5-8 | not in testing, general FTBFS: #1060951 libnss-pgsql_1.4.0debian-8 | not in testing, general FTBFS: #1066673 libpappsomspp_0.9.20-1 | not in testing, general FTBFS: #1064747 lintian-brush_0.152 | not in testing, general FTFTS: #0161435 newmat_1.10.4-8 | not in testing, general FTBFS: #1052790 newsboat_2.32-3 | not in testing, general FTBFS: #1054680 node-expat_2.4.0+ds-2 | not in testing, general FTBFS: #1064047 olive-editor_20221024+ds-1 | not in testing, general FTBFS: #1060206 onboard_1.4.1-5 | not in testing, general FTBFS: #1057442 openems_0.0.35+git20190103.6a75e98+dfsg.1-3.2 | not in testing, general FTBFS: #1054794 pixmap_2.6.6-1 | not in testing, general FTBFS: #1054698 procdump_1.2-4 | not in testing, riscv64 FTBFS: #1064137 raku-meta6_0.0.29-1 | not in testing, general FTBFS: #1057611 ruby-ruby-magic-static_0.6.0-2 | not in testing, general FTBFS: #1052749 rust-matchers_0.1.0-1 | not in testing, unsatisfiable build-dependency: #1054722 rust-mdl_1.0.4-1 | not in testing, general FTBFS: 1052952 rust-weedle_0.12.0-2 | not in testing, unsatisfiable build-dependency: #1007026 sdaps_1.9.8-0.1 | not in testing, general FTBFS: #1061159 segyio_1.8.3-1.2 | not in testing, general FTBFS: #1055728 swift-im_5.0~alpha2.145.g12d031cf8+dfsg-3 | not in testing, general FTBFS: #1056100 tetradraw_2.0.3-10 | not in testing, general FTBFS: #1057594 tomopy_1.14.1+ds1-1 | not in testing, general FTBFS: #1061064 The above packages are not in testing for various reasons, so they are not relevant for testing migration. Still if people want to look at them, the priority would be to look at the riscv64 specific issues, as for those, the packages might migrate to testing again at some point. * Packages kept due to cruft libapache-db-perl_0.18-2 | cruft, newer version in testing and unstable libevent_2.1.12-stable-8 | cruft, newer version in testing and unstable libpsl_0.21.2-1 | cruft, newer version in testing and unstable rust-bindgen_0.60.1-2 | cruft, newer version in testing and unstable rust-env-logger_0.9.3-1 | cruft, newer version in testing and unstable Those packages are kept in the archive to satisfy dependencies in other packages. This is not really an issue, and fixing the issue from the previous section will very likely clear all of them. [1] https://buildd.debian.org/tmp/~aurel32/riscv64rebuild.txt -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://aurel32.net
Attachment:
signature.asc
Description: PGP signature