Debian Bug report logs - #1121479
binNMU r-* for reproduce.debian.net

Reply or subscribe to this bug.

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Jochen Sprickerhof <jspricke@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: binNMU r-* for reproduce.debian.net

Date: Thu, 27 Nov 2025 10:01:22 +0100

Package: release.debian.org
Severity: normal
X-Debbugs-Cc: debian-r@lists.debian.org, Reproducible Builds discussion list <reproducible-builds@lists.alioth.debian.org>
User: release.debian.org@packages.debian.org
Usertags: binnmu

Hi,

we propose to binNMU the r-* packages after #1089197 was closed. Note that this
will alter the Recommends: and Suggests: of the package.

Thanks

Jochen and Paul (elbrus)


amd64:

fgarch_4033.92-1
lme4_1.1-37-1
r-bioc-affxparser_1.78.0-3
r-bioc-alabaster.base_1.6.1+ds-2
r-bioc-alabaster.matrix_1.6.1+ds-2
r-bioc-basilisk_1.18.0+ds-2
r-bioc-biobase_2.66.0-2
r-bioc-biocneighbors_2.0.1+ds-2
r-bioc-biocparallel_1.40.0-2
r-bioc-biocsingular_1.22.0+ds-2
r-bioc-bluster_1.16.0+dfsg-2
r-bioc-chemminer_3.58.0+dfsg-2
r-bioc-delayedarray_0.32.0+dfsg-2
r-bioc-densvis_1.16.0+dfsg-2
r-bioc-dirichletmultinomial_1.48.0-2
r-bioc-edger_4.4.2+dfsg-1
r-bioc-eir_1.46.0+ds-2
r-bioc-fmcsr_1.48.0+dfsg-2
r-bioc-graph_1.84.1-2
r-bioc-hdf5array_1.34.0-2
r-bioc-hilbertvis_1.64.0-2
r-bioc-iranges_2.40.1-3
r-bioc-limma_3.62.2+dfsg-1
r-bioc-lpsymphony_1.34.0+dfsg-3
r-bioc-metapod_1.14.0+dfsg-2
r-bioc-monocle_2.34.0-2
r-bioc-multtest_2.62.0-2
r-bioc-pcamethods_1.98.0-2
r-bioc-rbgl_1.82.0+dfsg-2
r-bioc-rhdf5_2.50.2+dfsg-1
r-bioc-rhdf5filters_1.18.1+dfsg-1
r-bioc-rhtslib_3.2.0+dfsg-2
r-bioc-rots_1.34.0-2
r-bioc-s4arrays_1.6.0+dfsg-2
r-bioc-s4vectors_0.44.0+dfsg-2
r-bioc-snpstats_1.56.0+dfsg-2
r-bioc-sparsearray_1.6.2+dfsg-2
r-bioc-sparsematrixstats_1.18.0+dfsg-2
r-bioc-xvector_0.46.0-2
r-cran-ade4_1.7-23-1
r-cran-adegenet_2.1.11-1
r-cran-adephylo_1.1-17-1
r-cran-amap_0.8-20-2
r-cran-amelia_1.8.3-1
r-cran-apcluster_1.4.13-1
r-cran-ape_5.8-1-1
r-cran-askpass_1.2.1-1
r-cran-base64url_1.4-2
r-cran-batchtools_0.9.17+dfsg-1
r-cran-bayesfactor_0.9.12-4.7+dfsg-1
r-cran-bayesm_3.1-6+dfsg-1
r-cran-bbmisc_1.13-1
r-cran-bdgraph_2.73+dfsg-1
r-cran-bench_1.1.4-1
r-cran-bigmemory_4.6.4-2
r-cran-bindrcpp_0.2.3-1
r-cran-bio3d_2.4-5-1
r-cran-bit_4.6.0+dfsg-1
r-cran-bit64_4.6.0-1-4
r-cran-blockmodeling_1.1.5-1
r-cran-brglm_0.7.2-1
r-cran-brglm2_0.9.2+dfsg-1
r-cran-brio_1.1.5-1
r-cran-cachem_1.1.0-1
r-cran-cairo_1.6-2-1
r-cran-caret_7.0-1+dfsg-1
r-cran-catools_1.18.3-1
r-cran-cba_0.2-25-1
r-cran-checkmate_2.3.2-1
r-cran-classint_0.4-11+dfsg-1
r-cran-cli_3.6.4-1
r-cran-clock_0.7.2-1
r-cran-clue_0.3-66-1
r-cran-coin_1.4-3-1
r-cran-collapse_2.1.0-1
r-cran-colorspace_2.1-1+dfsg-1
r-cran-commonmark_1.9.5-1
r-cran-covr_3.6.4+dfsg-1
r-cran-ctmcd_1.4.4+dfsg-1
r-cran-cutpointr_1.2.0-1
r-cran-data.table_1.17.0+dfsg-1
r-cran-dbscan_1.2.2+ds-2
r-cran-ddrtree_0.1.5-2
r-cran-decor_1.0.2-1
r-cran-deldir_2.0-4-1
r-cran-densityclust_0.3.3-1
r-cran-deoptim_2.2-8-1
r-cran-desolve_1.40-1
r-cran-dicedesign_1.10-1
r-cran-diffobj_0.3.5-1
r-cran-dimred_0.2.6-4
r-cran-distr_2.9.7+dfsg-1
r-cran-dosefinding_1.3-1-1
r-cran-dotcall64_1.2-1
r-cran-dplyr_1.1.4-4
r-cran-dqrng_0.3.2+dfsg-1
r-cran-earth_5.3.4-1
r-cran-ecosolver_0.5.5-1
r-cran-emoa_0.5-3-1
r-cran-estimatr_1.0.6-1
r-cran-etm_1.1.1-1
r-cran-evd_2.3-7.1-1
r-cran-exactextractr_0.10.0-1
r-cran-exactranktests_0.8-35-1
r-cran-expm_1.0-0-1
r-cran-extradistr_1.10.0-1
r-cran-factominer_2.11-1
r-cran-fansi_1.0.6-2
r-cran-farver_2.1.2-1
r-cran-fastmap_1.2.0-1
r-cran-ff_4.5.2+ds-1
r-cran-fields_16.3.1-1
r-cran-filelock_1.0.3-1
r-cran-fingerprint_3.5.7-2
r-cran-fnn_1.1.4.1-1
r-cran-forecast_8.23.0-1
r-cran-fracdiff_1.5-3-1
r-cran-fs_1.6.5+dfsg-1
r-cran-gam_1.22-5-1
r-cran-gap_1.6+dfsg-1
r-cran-gdtools_0.4.1-1
r-cran-gee_4.13-29-1
r-cran-genie_1.0.5-2
r-cran-geometry_0.5.2-1
r-cran-geosphere_1.5-20-1
r-cran-gert_2.1.4+dfsg-1
r-cran-ggforce_0.4.2-1
r-cran-ggraph_2.2.1+dfsg-1
r-cran-ggrepel_0.9.6-1
r-cran-glmmtmb_1.1.10+dfsg-1
r-cran-glmnet_4.1-8-1
r-cran-glue_1.8.0-1
r-cran-gmm_1.8-1
r-cran-gmp_0.7-5-1
r-cran-gnm_1.1-5-1
r-cran-gower_1.0.2-1
r-cran-graphlayouts_1.2.2-1
r-cran-gridtext_0.1.5-2
r-cran-haplo.stats_1.9.7-1
r-cran-hdf5r_1.3.12+dfsg-2
r-cran-hexbin_1.28.5-1
r-cran-htmltools_0.5.8.1-1
r-cran-httpuv_1.6.15+dfsg-1
r-cran-hunspell_3.0.5+dfsg-1
r-cran-influencer_0.1.5-1
r-cran-interp_1.1-6-1
r-cran-ipred_0.9-15-1
r-cran-irace_4.2.0-1
r-cran-isoband_0.2.7-1
r-cran-isospecr_2.1.3-1
r-cran-jinjar_0.3.2+dfsg-1
r-cran-jomo_2.7-6-1
r-cran-jsonlite_1.9.1+dfsg-1
r-cran-keyring_1.3.2-1
r-cran-knn.covertree_1.0-2
r-cran-ks_1.14.3-1
r-cran-lamw_2.2.4-1
r-cran-later_1.4.1+dfsg-1
r-cran-lavasearch2_2.0.3+dfsg-1
r-cran-lazyeval_0.2.2-1
r-cran-leidenbase_0.1.32-1
r-cran-lexrankr_0.5.2-8
r-cran-lhs_1.2.0-1
r-cran-libcoin_1.0-10-1
r-cran-lobstr_1.1.2-1
r-cran-locfit_1.5-9.12-1
r-cran-lubridate_1.9.4+dfsg-1
r-cran-luminescence_1.0.1-1
r-cran-magick_2.8.5+dfsg-1
r-cran-magrittr_2.0.3-1
r-cran-maldiquant_1.22.3-1
r-cran-maotai_0.2.6-1
r-cran-maps_3.4.2.1-1
r-cran-marginaleffects_0.25.0-1
r-cran-markovchain_0.10.0-1
r-cran-matching_4.10-15-1
r-cran-matchit_4.7.1-1
r-cran-matrixstats_1.5.0-1
r-cran-maxstat_0.7-25-2
r-cran-mclust_6.1.1-1
r-cran-mcmc_0.9-8-1
r-cran-mda_0.5-5-1
r-cran-memisc_0.99.31.8.2+dfsg-1
r-cran-mets_1.3.5+dfsg-1
r-cran-mice_3.17.0-1
r-cran-minerva_1.5.10-1
r-cran-minpack.lm_1.2-4-1
r-cran-mixsqp_0.3-54-1
r-cran-mlbench_2.1-6-1
r-cran-mlr_2.19.2+dfsg-1
r-cran-mnp_3.1-5-1
r-cran-modelmetrics_1.2.2.2-1
r-cran-msm_1.8.2-1
r-cran-mvnfast_0.2.8+dfsg-1
r-cran-nanoarrow_0.6.0-1
r-cran-network_1.19.0-1
r-cran-nmf_0.28-1
r-cran-nnls_1.6-1
r-cran-oaqc_2.0.0-1
r-cran-openmx_2.21.13+dfsg-1
r-cran-openssl_2.3.2+dfsg-1
r-cran-ordinal_2023.12-4.1-1
r-cran-pan_1.9-1
r-cran-pander_0.6.6+dfsg-1
r-cran-parallelly_1.42.0-1
r-cran-paramhelpers_1.14.2-1
r-cran-party_1.3-18-1
r-cran-partykit_1.2-23-1
r-cran-pcapp_2.0-5-1
r-cran-pcict_0.5-4.4-1
r-cran-pdftools_3.5.0-1
r-cran-pec_2023.04.12-1
r-cran-phangorn_2.12.1+dfsg-1
r-cran-phylobase_0.8.12-1
r-cran-pingr_2.0.5-1
r-cran-plyr_1.8.9-1
r-cran-poissonbinomial_1.2.7-1
r-cran-polycub_0.9.2-1
r-cran-princurve_2.1.6-1
r-cran-proc_1.18.5-1
r-cran-processx_3.8.6-1
r-cran-profvis_0.4.0+dfsg-1
r-cran-projpred_2.8.0+dfsg-1
r-cran-promises_1.3.2+dfsg-1
r-cran-prophet_1.0+dfsg-5
r-cran-proxy_0.4-27-1
r-cran-ps_1.9.0-1
r-cran-pscl_1.5.9-1
r-cran-psychotools_0.7-4-1
r-cran-purrr_1.0.4-1
r-cran-purrrlyr_0.0.8-1
r-cran-qap_0.1-2-1
r-cran-qgam_1.3.4-1
r-cran-qgraph_1.9.8-2
r-cran-qpdf_1.3.4+dfsg-2
r-cran-qqconf_1.3.2+dfsg-1
r-cran-qtl_1.70-1
r-cran-quickjsr_1.6.0-1
r-cran-ragg_1.3.3-1
r-cran-randomforest_4.7-1.2-1
r-cran-ranger_0.17.0-1
r-cran-rann_2.6.2-1
r-cran-rappdirs_0.3.3-1
r-cran-rbibutils_2.3-1
r-cran-rcppannoy_0.0.22-1
r-cran-rcppdist_0.1.1-2
r-cran-rcpphnsw_0.6.0+ds-1
r-cran-rcppml_0.3.7-2
r-cran-rcppparallel_5.1.7+dfsg-6
r-cran-rcpproll_0.3.1-1
r-cran-rcpptoml_0.2.3+dfsg-1
r-cran-rcurl_1.98-1.16+dfsg-1
r-cran-redland_1.0.17-18-1
r-cran-regsem_1.9.5+dfsg-1
r-cran-renv_1.1.2-1
r-cran-reshape2_1.4.4-2
r-cran-restfulr_0.0.15-1
r-cran-reticulate_1.41.0.1+dfsg-1
r-cran-rgenoud_5.9-0.11-1
r-cran-riskregression_2023.12.21+ds-1
r-cran-rjson_0.2.23-1
r-cran-rlang_1.1.5-3
r-cran-rle_0.9.2-2
r-cran-rmariadb_1.3.3+ds-1
r-cran-rmpfr_1.0-0-2
r-cran-rncl_0.8.7-1
r-cran-rnetcdf_2.9-2-1
r-cran-roxygen2_7.3.2-1
r-cran-rpact_4.2.0-1
r-cran-rpf_1.0.14+dfsg-1
r-cran-rprotobuf_0.4.23-1
r-cran-rrcov_1.7-6-1
r-cran-rspectra_0.16-2-1
r-cran-rsqlite_2.3.9-1
r-cran-rstan_2.32.7-1
r-cran-rstanarm_2.32.1-2
r-cran-rsvg_2.6.1-1
r-cran-rtdists_0.11-5-1
r-cran-rtsne_0.17-1
r-cran-rwiener_1.3-3-1
r-cran-s7_0.2.0-1
r-cran-samr_3.0-2
r-cran-sass_0.4.9+dfsg-1
r-cran-satellite_1.0.5+dfsg-1
r-cran-scattermore_1.2-1
r-cran-sctransform_0.4.1-1
r-cran-sem_3.1.16-1
r-cran-seriation_1.5.7-1
r-cran-sets_1.0.25+ds-1
r-cran-seurat_5.2.1-5
r-cran-seuratobject_5.0.2-1
r-cran-sitmo_2.0.2-1
r-cran-slider_0.3.2-1
r-cran-sna_2.8-1
r-cran-sodium_1.4.0+dfsg-1
r-cran-sourcetools_0.1.7-1-1
r-cran-sp_1:2.2-0+dfsg-1
r-cran-spam_2.11-1-1
r-cran-sparsevctrs_0.2.0-2
r-cran-spatialreg_1.3-6+dfsg-1
r-cran-spatstat.geom_3.3-6-1
r-cran-spatstat.linnet_3.2-5-1
r-cran-spatstat.model_3.3-4-1
r-cran-spatstat.random_3.3-3-1
r-cran-spatstat.utils_3.1-3-1
r-cran-spdep_1.3-5+dfsg-1
r-cran-splines2_0.5.4-1
r-cran-stanheaders_2.32.10-1
r-cran-statip_0.2.3-2
r-cran-statmod_1.5.0-1
r-cran-statnet.common_4.11.0-1
r-cran-stringdist_0.9.15-1
r-cran-surveillance_1.24.1-1
r-cran-survey_4.4-2-2
r-cran-svglite_2.1.3-2
r-cran-sys_3.4.3-1
r-cran-systemfonts_1.2.1-1
r-cran-testthat_3.2.3-1
r-cran-textshaping_0.3.7-2
r-cran-tfmpvalue_0.0.9-1
r-cran-tgp_2.4-23-1
r-cran-tibble_3.2.1+dfsg-3
r-cran-tidygraph_1.3.1-2
r-cran-tidyr_1.3.1-1
r-cran-tidyselect_1.2.1+dfsg-1
r-cran-tikzdevice_0.12.6-1
r-cran-timechange_0.3.0-2
r-cran-timereg_2.0.6-1
r-cran-tm_0.7-16-1
r-cran-tmb_1.9.17-1
r-cran-tmvtnorm_1.6-1
r-cran-tokenizers_0.3.0-1
r-cran-transformr_0.1.5-1
r-cran-treespace_1.1.4.3+dfsg-1
r-cran-triebeard_0.4.1-1
r-cran-truncnorm_1.0-9-2
r-cran-tsp_1.2-4-1
r-cran-tweenr_2.0.3-1
r-cran-ucminf_1.2.2-1
r-cran-units_0.8-7+dfsg-2
r-cran-urltools_1.7.3+dfsg-2
r-cran-utf8_1.2.4-1
r-cran-uwot_0.2.3-1
r-cran-vctrs_0.6.5-1
r-cran-vdiffr_1.0.8-1
r-cran-vegan_2.6-10+dfsg-3
r-cran-vgam_1.1-13-1
r-cran-vim_6.2.2+dfsg-1
r-cran-warp_0.2.1-1
r-cran-waveslim_1.8.5-1
r-cran-webfakes_1.3.2-1
r-cran-webutils_1.2.2-1
r-cran-wk_0.9.4-1
r-cran-wordcloud_2.6-2
r-cran-xfun_0.51+dfsg-1
r-cran-xts_0.14.1-1
r-cran-yaml_2.3.10-1
r-other-kcha-psiplot_2.3.0-2
r-other-x4r_1.0.1+git20150806.c6bd9bd-3


arm64:

fgarch_4033.92-1
lme4_1.1-37-1
r-bioc-affxparser_1.78.0-3
r-bioc-alabaster.base_1.6.1+ds-2
r-bioc-alabaster.matrix_1.6.1+ds-2
r-bioc-basilisk_1.18.0+ds-2
r-bioc-biobase_2.66.0-2
r-bioc-biocneighbors_2.0.1+ds-2
r-bioc-biocparallel_1.40.0-2
r-bioc-biocsingular_1.22.0+ds-2
r-bioc-bluster_1.16.0+dfsg-2
r-bioc-chemminer_3.58.0+dfsg-2
r-bioc-delayedarray_0.32.0+dfsg-2
r-bioc-densvis_1.16.0+dfsg-2
r-bioc-dirichletmultinomial_1.48.0-2
r-bioc-edger_4.4.2+dfsg-1
r-bioc-eir_1.46.0+ds-2
r-bioc-fmcsr_1.48.0+dfsg-2
r-bioc-graph_1.84.1-2
r-bioc-hdf5array_1.34.0-2
r-bioc-hilbertvis_1.64.0-2
r-bioc-iranges_2.40.1-3
r-bioc-limma_3.62.2+dfsg-1
r-bioc-lpsymphony_1.34.0+dfsg-3
r-bioc-metapod_1.14.0+dfsg-2
r-bioc-monocle_2.34.0-2
r-bioc-multtest_2.62.0-2
r-bioc-pcamethods_1.98.0-2
r-bioc-rbgl_1.82.0+dfsg-2
r-bioc-rhdf5_2.50.2+dfsg-1
r-bioc-rhdf5filters_1.18.1+dfsg-1
r-bioc-rhtslib_3.2.0+dfsg-2
r-bioc-rots_1.34.0-2
r-bioc-s4arrays_1.6.0+dfsg-2
r-bioc-s4vectors_0.44.0+dfsg-2
r-bioc-snpstats_1.56.0+dfsg-2
r-bioc-sparsearray_1.6.2+dfsg-2
r-bioc-sparsematrixstats_1.18.0+dfsg-2
r-bioc-xvector_0.46.0-2
r-cran-ade4_1.7-23-1
r-cran-adegenet_2.1.11-1
r-cran-adephylo_1.1-17-1
r-cran-amap_0.8-20-2
r-cran-amelia_1.8.3-1
r-cran-apcluster_1.4.13-1
r-cran-ape_5.8-1-1
r-cran-askpass_1.2.1-1
r-cran-base64url_1.4-2
r-cran-batchtools_0.9.17+dfsg-1
r-cran-bayesfactor_0.9.12-4.7+dfsg-1
r-cran-bayesm_3.1-6+dfsg-1
r-cran-bbmisc_1.13-1
r-cran-bdgraph_2.73+dfsg-1
r-cran-bench_1.1.4-1
r-cran-bigmemory_4.6.4-2
r-cran-bindrcpp_0.2.3-1
r-cran-bio3d_2.4-5-1
r-cran-bit_4.6.0+dfsg-1
r-cran-bit64_4.6.0-1-4
r-cran-blockmodeling_1.1.5-1
r-cran-brglm_0.7.2-1
r-cran-brglm2_0.9.2+dfsg-1
r-cran-brio_1.1.5-1
r-cran-cachem_1.1.0-1
r-cran-cairo_1.6-2-1
r-cran-caret_7.0-1+dfsg-1
r-cran-catools_1.18.3-1
r-cran-cba_0.2-25-1
r-cran-checkmate_2.3.2-1
r-cran-classint_0.4-11+dfsg-1
r-cran-cli_3.6.4-1
r-cran-clock_0.7.2-1
r-cran-clue_0.3-66-1
r-cran-coin_1.4-3-1
r-cran-collapse_2.1.0-1
r-cran-colorspace_2.1-1+dfsg-1
r-cran-commonmark_1.9.5-1
r-cran-covr_3.6.4+dfsg-1
r-cran-ctmcd_1.4.4+dfsg-1
r-cran-cutpointr_1.2.0-1
r-cran-data.table_1.17.0+dfsg-1
r-cran-dbscan_1.2.2+ds-2
r-cran-decor_1.0.2-1
r-cran-deldir_2.0-4-1
r-cran-densityclust_0.3.3-1
r-cran-deoptim_2.2-8-1
r-cran-desolve_1.40-1
r-cran-dicedesign_1.10-1
r-cran-diffobj_0.3.5-1
r-cran-dimred_0.2.6-4
r-cran-distr_2.9.7+dfsg-1
r-cran-dosefinding_1.3-1-1
r-cran-dotcall64_1.2-1
r-cran-dplyr_1.1.4-4
r-cran-dqrng_0.3.2+dfsg-1
r-cran-earth_5.3.4-1
r-cran-ecosolver_0.5.5-1
r-cran-emoa_0.5-3-1
r-cran-estimatr_1.0.6-1
r-cran-etm_1.1.1-1
r-cran-evd_2.3-7.1-1
r-cran-exactextractr_0.10.0-1
r-cran-exactranktests_0.8-35-1
r-cran-expm_1.0-0-1
r-cran-extradistr_1.10.0-1
r-cran-factominer_2.11-1
r-cran-fansi_1.0.6-2
r-cran-farver_2.1.2-1
r-cran-fastmap_1.2.0-1
r-cran-ff_4.5.2+ds-1
r-cran-fields_16.3.1-1
r-cran-filelock_1.0.3-1
r-cran-fingerprint_3.5.7-2
r-cran-fnn_1.1.4.1-1
r-cran-forecast_8.23.0-1
r-cran-fracdiff_1.5-3-1
r-cran-fs_1.6.5+dfsg-1
r-cran-gam_1.22-5-1
r-cran-gap_1.6+dfsg-1
r-cran-gdtools_0.4.1-1
r-cran-gee_4.13-29-1
r-cran-genie_1.0.5-2
r-cran-geometry_0.5.2-1
r-cran-geosphere_1.5-20-1
r-cran-gert_2.1.4+dfsg-1
r-cran-ggforce_0.4.2-1
r-cran-ggraph_2.2.1+dfsg-1
r-cran-ggrepel_0.9.6-1
r-cran-glmmtmb_1.1.10+dfsg-1
r-cran-glmnet_4.1-8-1
r-cran-glue_1.8.0-1
r-cran-gmm_1.8-1
r-cran-gmp_0.7-5-1
r-cran-gnm_1.1-5-1
r-cran-gower_1.0.2-1
r-cran-graphlayouts_1.2.2-1
r-cran-gridtext_0.1.5-2
r-cran-haplo.stats_1.9.7-1
r-cran-hdf5r_1.3.12+dfsg-2
r-cran-hexbin_1.28.5-1
r-cran-htmltools_0.5.8.1-1
r-cran-httpuv_1.6.15+dfsg-1
r-cran-hunspell_3.0.5+dfsg-1
r-cran-influencer_0.1.5-1
r-cran-interp_1.1-6-1
r-cran-ipred_0.9-15-1
r-cran-irace_4.2.0-1
r-cran-isoband_0.2.7-1
r-cran-isospecr_2.1.3-1
r-cran-jinjar_0.3.2+dfsg-1
r-cran-jomo_2.7-6-1
r-cran-jsonlite_1.9.1+dfsg-1
r-cran-keyring_1.3.2-1
r-cran-knn.covertree_1.0-2
r-cran-ks_1.14.3-1
r-cran-lamw_2.2.4-1
r-cran-later_1.4.1+dfsg-1
r-cran-lavasearch2_2.0.3+dfsg-1
r-cran-lazyeval_0.2.2-1
r-cran-leidenbase_0.1.32-1
r-cran-lexrankr_0.5.2-8
r-cran-lhs_1.2.0-1
r-cran-libcoin_1.0-10-1
r-cran-lobstr_1.1.2-1
r-cran-locfit_1.5-9.12-1
r-cran-lubridate_1.9.4+dfsg-1
r-cran-luminescence_1.0.1-1
r-cran-magick_2.8.5+dfsg-1
r-cran-magrittr_2.0.3-1
r-cran-maldiquant_1.22.3-1
r-cran-maotai_0.2.6-1
r-cran-maps_3.4.2.1-1
r-cran-marginaleffects_0.25.0-1
r-cran-matching_4.10-15-1
r-cran-matchit_4.7.1-1
r-cran-matrixstats_1.5.0-1
r-cran-maxstat_0.7-25-2
r-cran-mclust_6.1.1-1
r-cran-mcmc_0.9-8-1
r-cran-mda_0.5-5-1
r-cran-memisc_0.99.31.8.2+dfsg-1
r-cran-mets_1.3.5+dfsg-1
r-cran-mice_3.17.0-1
r-cran-minerva_1.5.10-1
r-cran-minpack.lm_1.2-4-1
r-cran-mixsqp_0.3-54-1
r-cran-mlbench_2.1-6-1
r-cran-mlr_2.19.2+dfsg-1
r-cran-mnp_3.1-5-1
r-cran-modelmetrics_1.2.2.2-1
r-cran-msm_1.8.2-1
r-cran-mvnfast_0.2.8+dfsg-1
r-cran-nanoarrow_0.6.0-1
r-cran-network_1.19.0-1
r-cran-nmf_0.28-1
r-cran-nnls_1.6-1
r-cran-oaqc_2.0.0-1
r-cran-openmx_2.21.13+dfsg-1
r-cran-openssl_2.3.2+dfsg-1
r-cran-ordinal_2023.12-4.1-1
r-cran-pan_1.9-1
r-cran-pander_0.6.6+dfsg-1
r-cran-parallelly_1.42.0-1
r-cran-paramhelpers_1.14.2-1
r-cran-party_1.3-18-1
r-cran-partykit_1.2-23-1
r-cran-pcapp_2.0-5-1
r-cran-pcict_0.5-4.4-1
r-cran-pdftools_3.5.0-1
r-cran-pec_2023.04.12-1
r-cran-phangorn_2.12.1+dfsg-1
r-cran-phylobase_0.8.12-1
r-cran-pingr_2.0.5-1
r-cran-plyr_1.8.9-1
r-cran-poissonbinomial_1.2.7-1
r-cran-polycub_0.9.2-1
r-cran-princurve_2.1.6-1
r-cran-proc_1.18.5-1
r-cran-processx_3.8.6-1
r-cran-profvis_0.4.0+dfsg-1
r-cran-projpred_2.8.0+dfsg-1
r-cran-promises_1.3.2+dfsg-1
r-cran-prophet_1.0+dfsg-5
r-cran-proxy_0.4-27-1
r-cran-ps_1.9.0-1
r-cran-pscl_1.5.9-1
r-cran-psychotools_0.7-4-1
r-cran-purrr_1.0.4-1
r-cran-purrrlyr_0.0.8-1
r-cran-qap_0.1-2-1
r-cran-qgam_1.3.4-1
r-cran-qgraph_1.9.8-2
r-cran-qpdf_1.3.4+dfsg-2
r-cran-qqconf_1.3.2+dfsg-1
r-cran-qtl_1.70-1
r-cran-quickjsr_1.6.0-1
r-cran-ragg_1.3.3-1
r-cran-randomforest_4.7-1.2-1
r-cran-ranger_0.17.0-1
r-cran-rann_2.6.2-1
r-cran-rappdirs_0.3.3-1
r-cran-rbibutils_2.3-1
r-cran-rcppannoy_0.0.22-1
r-cran-rcppdist_0.1.1-2
r-cran-rcpphnsw_0.6.0+ds-1
r-cran-rcppml_0.3.7-2
r-cran-rcppparallel_5.1.7+dfsg-6
r-cran-rcpproll_0.3.1-1
r-cran-rcpptoml_0.2.3+dfsg-1
r-cran-rcurl_1.98-1.16+dfsg-1
r-cran-redland_1.0.17-18-1
r-cran-regsem_1.9.5+dfsg-1
r-cran-renv_1.1.2-1
r-cran-reshape2_1.4.4-2
r-cran-restfulr_0.0.15-1
r-cran-reticulate_1.41.0.1+dfsg-1
r-cran-rgenoud_5.9-0.11-1
r-cran-riskregression_2023.12.21+ds-1
r-cran-rjson_0.2.23-1
r-cran-rlang_1.1.5-3
r-cran-rle_0.9.2-2
r-cran-rlrsim_3.1-8-1
r-cran-rmariadb_1.3.3+ds-1
r-cran-rmpfr_1.0-0-2
r-cran-rncl_0.8.7-1
r-cran-rnetcdf_2.9-2-1
r-cran-roxygen2_7.3.2-1
r-cran-rpact_4.2.0-1
r-cran-rpf_1.0.14+dfsg-1
r-cran-rprotobuf_0.4.23-1
r-cran-rrcov_1.7-6-1
r-cran-rspectra_0.16-2-1
r-cran-rsqlite_2.3.9-1
r-cran-rstan_2.32.7-1
r-cran-rstanarm_2.32.1-2
r-cran-rsvg_2.6.1-1
r-cran-rtdists_0.11-5-1
r-cran-rtsne_0.17-1
r-cran-rwiener_1.3-3-1
r-cran-s7_0.2.0-1
r-cran-sass_0.4.9+dfsg-1
r-cran-satellite_1.0.5+dfsg-1
r-cran-scattermore_1.2-1
r-cran-sctransform_0.4.1-1
r-cran-sem_3.1.16-1
r-cran-seriation_1.5.7-1
r-cran-sets_1.0.25+ds-1
r-cran-seurat_5.2.1-5
r-cran-seuratobject_5.0.2-1
r-cran-sitmo_2.0.2-1
r-cran-slider_0.3.2-1
r-cran-sna_2.8-1
r-cran-sodium_1.4.0+dfsg-1
r-cran-sourcetools_0.1.7-1-1
r-cran-sp_1:2.2-0+dfsg-1
r-cran-spam_2.11-1-1
r-cran-sparsesvd_0.2-2-1
r-cran-sparsevctrs_0.2.0-2
r-cran-spatialreg_1.3-6+dfsg-1
r-cran-spatstat.explore_3.3-4-1
r-cran-spatstat.geom_3.3-6-1
r-cran-spatstat.linnet_3.2-5-1
r-cran-spatstat.model_3.3-4-1
r-cran-spatstat.random_3.3-3-1
r-cran-spatstat.utils_3.1-3-1
r-cran-spdep_1.3-5+dfsg-1
r-cran-splines2_0.5.4-1
r-cran-stanheaders_2.32.10-1
r-cran-statip_0.2.3-2
r-cran-statmod_1.5.0-1
r-cran-statnet.common_4.11.0-1
r-cran-stringdist_0.9.15-1
r-cran-surveillance_1.24.1-1
r-cran-survey_4.4-2-2
r-cran-svglite_2.1.3-2
r-cran-sys_3.4.3-1
r-cran-systemfonts_1.2.1-1
r-cran-testthat_3.2.3-1
r-cran-textshaping_0.3.7-2
r-cran-tfmpvalue_0.0.9-1
r-cran-tgp_2.4-23-1
r-cran-tibble_3.2.1+dfsg-3
r-cran-tidygraph_1.3.1-2
r-cran-tidyr_1.3.1-1
r-cran-tidyselect_1.2.1+dfsg-1
r-cran-tikzdevice_0.12.6-1
r-cran-timechange_0.3.0-2
r-cran-timereg_2.0.6-1
r-cran-tm_0.7-16-1
r-cran-tmb_1.9.17-1
r-cran-tmvtnorm_1.6-1
r-cran-tokenizers_0.3.0-1
r-cran-transformr_0.1.5-1
r-cran-treespace_1.1.4.3+dfsg-1
r-cran-triebeard_0.4.1-1
r-cran-truncnorm_1.0-9-2
r-cran-tsp_1.2-4-1
r-cran-tweenr_2.0.3-1
r-cran-ucminf_1.2.2-1
r-cran-units_0.8-7+dfsg-2
r-cran-urltools_1.7.3+dfsg-2
r-cran-utf8_1.2.4-1
r-cran-uwot_0.2.3-1
r-cran-vctrs_0.6.5-1
r-cran-vdiffr_1.0.8-1
r-cran-vegan_2.6-10+dfsg-3
r-cran-vgam_1.1-13-1
r-cran-vim_6.2.2+dfsg-1
r-cran-warp_0.2.1-1
r-cran-waveslim_1.8.5-1
r-cran-webfakes_1.3.2-1
r-cran-webutils_1.2.2-1
r-cran-wk_0.9.4-1
r-cran-wordcloud_2.6-2
r-cran-xfun_0.51+dfsg-1
r-cran-xts_0.14.1-1
r-cran-yaml_2.3.10-1
r-other-kcha-psiplot_2.3.0-2


armhf:

fgarch_4033.92-1
lme4_1.1-37-1
r-bioc-biobase_2.66.0-2
r-bioc-s4vectors_0.44.0+dfsg-2
r-cran-ade4_1.7-23-1
r-cran-adegenet_2.1.11-1
r-cran-adephylo_1.1-17-1
r-cran-amap_0.8-20-2
r-cran-amelia_1.8.3-1
r-cran-apcluster_1.4.13-1
r-cran-ape_5.8-1-1
r-cran-askpass_1.2.1-1
r-cran-base64url_1.4-2
r-cran-batchtools_0.9.17+dfsg-1
r-cran-bayesfactor_0.9.12-4.7+dfsg-1
r-cran-bayesm_3.1-6+dfsg-1
r-cran-bbmisc_1.13-1
r-cran-bdgraph_2.73+dfsg-1
r-cran-bench_1.1.4-1
r-cran-bigmemory_4.6.4-2
r-cran-bindrcpp_0.2.3-1
r-cran-bio3d_2.4-5-1
r-cran-bit_4.6.0+dfsg-1
r-cran-bit64_4.6.0-1-4
r-cran-blockmodeling_1.1.5-1
r-cran-brglm_0.7.2-1
r-cran-brglm2_0.9.2+dfsg-1
r-cran-brio_1.1.5-1
r-cran-cachem_1.1.0-1
r-cran-cairo_1.6-2-1
r-cran-caret_7.0-1+dfsg-1
r-cran-catools_1.18.3-1
r-cran-cba_0.2-25-1
r-cran-checkmate_2.3.2-1
r-cran-classint_0.4-11+dfsg-1
r-cran-cli_3.6.4-1
r-cran-clock_0.7.2-1
r-cran-clue_0.3-66-1
r-cran-coin_1.4-3-1
r-cran-collapse_2.1.0-1
r-cran-colorspace_2.1-1+dfsg-1
r-cran-commonmark_1.9.5-1
r-cran-covr_3.6.4+dfsg-1
r-cran-ctmcd_1.4.4+dfsg-1
r-cran-cutpointr_1.2.0-1
r-cran-data.table_1.17.0+dfsg-1
r-cran-dbscan_1.2.2+ds-2
r-cran-ddrtree_0.1.5-2
r-cran-decor_1.0.2-1
r-cran-deldir_2.0-4-1
r-cran-densityclust_0.3.3-1
r-cran-deoptim_2.2-8-1
r-cran-desolve_1.40-1
r-cran-dicedesign_1.10-1
r-cran-diffobj_0.3.5-1
r-cran-distr_2.9.7+dfsg-1
r-cran-dosefinding_1.3-1-1
r-cran-dotcall64_1.2-1
r-cran-dplyr_1.1.4-4
r-cran-dqrng_0.3.2+dfsg-1
r-cran-earth_5.3.4-1
r-cran-ecosolver_0.5.5-1
r-cran-emoa_0.5-3-1
r-cran-estimatr_1.0.6-1
r-cran-etm_1.1.1-1
r-cran-evd_2.3-7.1-1
r-cran-exactextractr_0.10.0-1
r-cran-exactranktests_0.8-35-1
r-cran-expm_1.0-0-1
r-cran-extradistr_1.10.0-1
r-cran-factominer_2.11-1
r-cran-fansi_1.0.6-2
r-cran-farver_2.1.2-1
r-cran-fastmap_1.2.0-1
r-cran-ff_4.5.2+ds-1
r-cran-fields_16.3.1-1
r-cran-filelock_1.0.3-1
r-cran-fingerprint_3.5.7-2
r-cran-fnn_1.1.4.1-1
r-cran-forecast_8.23.0-1
r-cran-fracdiff_1.5-3-1
r-cran-fs_1.6.5+dfsg-1
r-cran-gam_1.22-5-1
r-cran-gap_1.6+dfsg-1
r-cran-gdtools_0.4.1-1
r-cran-gee_4.13-29-1
r-cran-genie_1.0.5-2
r-cran-geometry_0.5.2-1
r-cran-geosphere_1.5-20-1
r-cran-gert_2.1.4+dfsg-1
r-cran-ggforce_0.4.2-1
r-cran-ggraph_2.2.1+dfsg-1
r-cran-ggrepel_0.9.6-1
r-cran-glmnet_4.1-8-1
r-cran-glue_1.8.0-1
r-cran-gmm_1.8-1
r-cran-gmp_0.7-5-1
r-cran-gnm_1.1-5-1
r-cran-gower_1.0.2-1
r-cran-graphlayouts_1.2.2-1
r-cran-gridtext_0.1.5-2
r-cran-haplo.stats_1.9.7-1
r-cran-hdf5r_1.3.12+dfsg-2
r-cran-hexbin_1.28.5-1
r-cran-htmltools_0.5.8.1-1
r-cran-httpuv_1.6.15+dfsg-1
r-cran-hunspell_3.0.5+dfsg-1
r-cran-influencer_0.1.5-1
r-cran-interp_1.1-6-1
r-cran-ipred_0.9-15-1
r-cran-irace_4.2.0-1
r-cran-isoband_0.2.7-1
r-cran-isospecr_2.1.3-1
r-cran-jinjar_0.3.2+dfsg-1
r-cran-jomo_2.7-6-1
r-cran-jsonlite_1.9.1+dfsg-1
r-cran-keyring_1.3.2-1
r-cran-knn.covertree_1.0-2
r-cran-ks_1.14.3-1
r-cran-lamw_2.2.4-1
r-cran-later_1.4.1+dfsg-1
r-cran-lavasearch2_2.0.3+dfsg-1
r-cran-lazyeval_0.2.2-1
r-cran-leidenbase_0.1.32-1
r-cran-lexrankr_0.5.2-8
r-cran-lhs_1.2.0-1
r-cran-libcoin_1.0-10-1
r-cran-lobstr_1.1.2-1
r-cran-locfit_1.5-9.12-1
r-cran-lubridate_1.9.4+dfsg-1
r-cran-luminescence_1.0.1-1
r-cran-magick_2.8.5+dfsg-1
r-cran-magrittr_2.0.3-1
r-cran-maldiquant_1.22.3-1
r-cran-maotai_0.2.6-1
r-cran-maps_3.4.2.1-1
r-cran-marginaleffects_0.25.0-1
r-cran-markovchain_0.10.0-1
r-cran-matching_4.10-15-1
r-cran-matchit_4.7.1-1
r-cran-matrixstats_1.5.0-1
r-cran-maxstat_0.7-25-2
r-cran-mclust_6.1.1-1
r-cran-mcmc_0.9-8-1
r-cran-mda_0.5-5-1
r-cran-memisc_0.99.31.8.2+dfsg-1
r-cran-mets_1.3.5+dfsg-1
r-cran-mice_3.17.0-1
r-cran-minerva_1.5.10-1
r-cran-minpack.lm_1.2-4-1
r-cran-mixsqp_0.3-54-1
r-cran-mlbench_2.1-6-1
r-cran-mlr_2.19.2+dfsg-1
r-cran-mnp_3.1-5-1
r-cran-modelmetrics_1.2.2.2-1
r-cran-msm_1.8.2-1
r-cran-mvnfast_0.2.8+dfsg-1
r-cran-nanoarrow_0.6.0-1
r-cran-network_1.19.0-1
r-cran-nmf_0.28-1
r-cran-nnls_1.6-1
r-cran-oaqc_2.0.0-1
r-cran-openmx_2.21.13+dfsg-1
r-cran-openssl_2.3.2+dfsg-1
r-cran-ordinal_2023.12-4.1-1
r-cran-pan_1.9-1
r-cran-pander_0.6.6+dfsg-1
r-cran-parallelly_1.42.0-1
r-cran-paramhelpers_1.14.2-1
r-cran-party_1.3-18-1
r-cran-partykit_1.2-23-1
r-cran-pcapp_2.0-5-1
r-cran-pcict_0.5-4.4-1
r-cran-pdftools_3.5.0-1
r-cran-pec_2023.04.12-1
r-cran-phangorn_2.12.1+dfsg-1
r-cran-phylobase_0.8.12-1
r-cran-pingr_2.0.5-1
r-cran-plyr_1.8.9-1
r-cran-poissonbinomial_1.2.7-1
r-cran-polycub_0.9.2-1
r-cran-princurve_2.1.6-1
r-cran-proc_1.18.5-1
r-cran-processx_3.8.6-1
r-cran-profvis_0.4.0+dfsg-1
r-cran-projpred_2.8.0+dfsg-1
r-cran-promises_1.3.2+dfsg-1
r-cran-prophet_1.0+dfsg-5
r-cran-proxy_0.4-27-1
r-cran-ps_1.9.0-1
r-cran-pscl_1.5.9-1
r-cran-psychotools_0.7-4-1
r-cran-purrr_1.0.4-1
r-cran-purrrlyr_0.0.8-1
r-cran-qap_0.1-2-1
r-cran-qgam_1.3.4-1
r-cran-qgraph_1.9.8-2
r-cran-qpdf_1.3.4+dfsg-2
r-cran-qqconf_1.3.2+dfsg-1
r-cran-qtl_1.70-1
r-cran-quickjsr_1.6.0-1
r-cran-ragg_1.3.3-1
r-cran-randomforest_4.7-1.2-1
r-cran-ranger_0.17.0-1
r-cran-rann_2.6.2-1
r-cran-rappdirs_0.3.3-1
r-cran-rbibutils_2.3-1
r-cran-rcppannoy_0.0.22-1
r-cran-rcppdist_0.1.1-2
r-cran-rcpphnsw_0.6.0+ds-1
r-cran-rcppml_0.3.7-2
r-cran-rcppparallel_5.1.7+dfsg-6
r-cran-rcpproll_0.3.1-1
r-cran-rcpptoml_0.2.3+dfsg-1
r-cran-rcurl_1.98-1.16+dfsg-1
r-cran-redland_1.0.17-18-1
r-cran-regsem_1.9.5+dfsg-1
r-cran-renv_1.1.2-1
r-cran-reshape2_1.4.4-2
r-cran-restfulr_0.0.15-1
r-cran-reticulate_1.41.0.1+dfsg-1
r-cran-rgenoud_5.9-0.11-1
r-cran-riskregression_2023.12.21+ds-1
r-cran-rjson_0.2.23-1
r-cran-rlang_1.1.5-3
r-cran-rle_0.9.2-2
r-cran-rmariadb_1.3.3+ds-1
r-cran-rmpfr_1.0-0-2
r-cran-rncl_0.8.7-1
r-cran-rnetcdf_2.9-2-1
r-cran-roxygen2_7.3.2-1
r-cran-rpact_4.2.0-1
r-cran-rpf_1.0.14+dfsg-1
r-cran-rprotobuf_0.4.23-1
r-cran-rrcov_1.7-6-1
r-cran-rspectra_0.16-2-1
r-cran-rsqlite_2.3.9-1
r-cran-rstan_2.32.7-1
r-cran-rstanarm_2.32.1-2
r-cran-rsvg_2.6.1-1
r-cran-rtdists_0.11-5-1
r-cran-rtsne_0.17-1
r-cran-rwiener_1.3-3-1
r-cran-s7_0.2.0-1
r-cran-samr_3.0-2
r-cran-sass_0.4.9+dfsg-1
r-cran-satellite_1.0.5+dfsg-1
r-cran-scattermore_1.2-1
r-cran-sctransform_0.4.1-1
r-cran-sem_3.1.16-1
r-cran-seriation_1.5.7-1
r-cran-sets_1.0.25+ds-1
r-cran-seurat_5.2.1-5
r-cran-seuratobject_5.0.2-1
r-cran-sitmo_2.0.2-1
r-cran-slider_0.3.2-1
r-cran-sna_2.8-1
r-cran-sodium_1.4.0+dfsg-1
r-cran-sourcetools_0.1.7-1-1
r-cran-sp_1:2.2-0+dfsg-1
r-cran-spam_2.11-1-1
r-cran-sparsevctrs_0.2.0-2
r-cran-spatialreg_1.3-6+dfsg-1
r-cran-spatstat.explore_3.3-4-1
r-cran-spatstat.geom_3.3-6-1
r-cran-spatstat.linnet_3.2-5-1
r-cran-spatstat.model_3.3-4-1
r-cran-spatstat.random_3.3-3-1
r-cran-spatstat.utils_3.1-3-1
r-cran-spdep_1.3-5+dfsg-1
r-cran-splines2_0.5.4-1
r-cran-stanheaders_2.32.10-1
r-cran-statip_0.2.3-2
r-cran-statmod_1.5.0-1
r-cran-statnet.common_4.11.0-1
r-cran-stringdist_0.9.15-1
r-cran-surveillance_1.24.1-1
r-cran-survey_4.4-2-2
r-cran-svglite_2.1.3-2
r-cran-sys_3.4.3-1
r-cran-systemfonts_1.2.1-1
r-cran-testthat_3.2.3-1
r-cran-textshaping_0.3.7-2
r-cran-tfmpvalue_0.0.9-1
r-cran-tgp_2.4-23-1
r-cran-tibble_3.2.1+dfsg-3
r-cran-tidygraph_1.3.1-2
r-cran-tidyr_1.3.1-1
r-cran-tidyselect_1.2.1+dfsg-1
r-cran-tikzdevice_0.12.6-1
r-cran-timechange_0.3.0-2
r-cran-timereg_2.0.6-1
r-cran-tm_0.7-16-1
r-cran-tmvtnorm_1.6-1
r-cran-tokenizers_0.3.0-1
r-cran-transformr_0.1.5-1
r-cran-treespace_1.1.4.3+dfsg-1
r-cran-triebeard_0.4.1-1
r-cran-truncnorm_1.0-9-2
r-cran-tsp_1.2-4-1
r-cran-tweenr_2.0.3-1
r-cran-ucminf_1.2.2-1
r-cran-units_0.8-7+dfsg-2
r-cran-urltools_1.7.3+dfsg-2
r-cran-utf8_1.2.4-1
r-cran-uwot_0.2.3-1
r-cran-vctrs_0.6.5-1
r-cran-vdiffr_1.0.8-1
r-cran-vegan_2.6-10+dfsg-3
r-cran-vgam_1.1-13-1
r-cran-vim_6.2.2+dfsg-1
r-cran-warp_0.2.1-1
r-cran-waveslim_1.8.5-1
r-cran-webfakes_1.3.2-1
r-cran-webutils_1.2.2-1
r-cran-wk_0.9.4-1
r-cran-wordcloud_2.6-2
r-cran-xfun_0.51+dfsg-1
r-cran-xts_0.14.1-1
r-cran-yaml_2.3.10-1
r-other-kcha-psiplot_2.3.0-2
r-other-x4r_1.0.1+git20150806.c6bd9bd-3


i386:

fgarch_4033.92-1
lme4_1.1-37-1
r-bioc-biobase_2.66.0-2
r-bioc-s4vectors_0.44.0+dfsg-2
r-cran-ade4_1.7-23-1
r-cran-adegenet_2.1.11-1
r-cran-adephylo_1.1-17-1
r-cran-amap_0.8-20-2
r-cran-amelia_1.8.3-1
r-cran-apcluster_1.4.13-1
r-cran-ape_5.8-1-1
r-cran-askpass_1.2.1-1
r-cran-base64url_1.4-2
r-cran-batchtools_0.9.17+dfsg-1
r-cran-bayesfactor_0.9.12-4.7+dfsg-1
r-cran-bayesm_3.1-6+dfsg-1
r-cran-bbmisc_1.13-1
r-cran-bdgraph_2.73+dfsg-1
r-cran-bench_1.1.4-1
r-cran-bigmemory_4.6.4-2
r-cran-bindrcpp_0.2.3-1
r-cran-bio3d_2.4-5-1
r-cran-bit_4.6.0+dfsg-1
r-cran-bit64_4.6.0-1-4
r-cran-blockmodeling_1.1.5-1
r-cran-brglm_0.7.2-1
r-cran-brglm2_0.9.2+dfsg-1
r-cran-brio_1.1.5-1
r-cran-cachem_1.1.0-1
r-cran-cairo_1.6-2-1
r-cran-caret_7.0-1+dfsg-1
r-cran-catools_1.18.3-1
r-cran-cba_0.2-25-1
r-cran-checkmate_2.3.2-1
r-cran-classint_0.4-11+dfsg-1
r-cran-cli_3.6.4-1
r-cran-clock_0.7.2-1
r-cran-clue_0.3-66-1
r-cran-coin_1.4-3-1
r-cran-collapse_2.1.0-1
r-cran-colorspace_2.1-1+dfsg-1
r-cran-commonmark_1.9.5-1
r-cran-covr_3.6.4+dfsg-1
r-cran-ctmcd_1.4.4+dfsg-1
r-cran-cutpointr_1.2.0-1
r-cran-data.table_1.17.0+dfsg-1
r-cran-dbscan_1.2.2+ds-2
r-cran-ddrtree_0.1.5-2
r-cran-decor_1.0.2-1
r-cran-deldir_2.0-4-1
r-cran-densityclust_0.3.3-1
r-cran-deoptim_2.2-8-1
r-cran-desolve_1.40-1
r-cran-dicedesign_1.10-1
r-cran-diffobj_0.3.5-1
r-cran-distr_2.9.7+dfsg-1
r-cran-dosefinding_1.3-1-1
r-cran-dotcall64_1.2-1
r-cran-dplyr_1.1.4-4
r-cran-dqrng_0.3.2+dfsg-1
r-cran-earth_5.3.4-1
r-cran-ecosolver_0.5.5-1
r-cran-emoa_0.5-3-1
r-cran-estimatr_1.0.6-1
r-cran-etm_1.1.1-1
r-cran-evd_2.3-7.1-1
r-cran-exactextractr_0.10.0-1
r-cran-exactranktests_0.8-35-1
r-cran-expm_1.0-0-1
r-cran-extradistr_1.10.0-1
r-cran-factominer_2.11-1
r-cran-fansi_1.0.6-2
r-cran-farver_2.1.2-1
r-cran-fastmap_1.2.0-1
r-cran-ff_4.5.2+ds-1
r-cran-fields_16.3.1-1
r-cran-filelock_1.0.3-1
r-cran-fingerprint_3.5.7-2
r-cran-fnn_1.1.4.1-1
r-cran-forecast_8.23.0-1
r-cran-fracdiff_1.5-3-1
r-cran-fs_1.6.5+dfsg-1
r-cran-gam_1.22-5-1
r-cran-gap_1.6+dfsg-1
r-cran-gdtools_0.4.1-1
r-cran-gee_4.13-29-1
r-cran-genie_1.0.5-2
r-cran-geometry_0.5.2-1
r-cran-geosphere_1.5-20-1
r-cran-gert_2.1.4+dfsg-1
r-cran-ggforce_0.4.2-1
r-cran-ggraph_2.2.1+dfsg-1
r-cran-ggrepel_0.9.6-1
r-cran-glmnet_4.1-8-1
r-cran-glue_1.8.0-1
r-cran-gmm_1.8-1
r-cran-gmp_0.7-5-1
r-cran-gnm_1.1-5-1
r-cran-gower_1.0.2-1
r-cran-graphlayouts_1.2.2-1
r-cran-gridtext_0.1.5-2
r-cran-haplo.stats_1.9.7-1
r-cran-hdf5r_1.3.12+dfsg-2
r-cran-hexbin_1.28.5-1
r-cran-htmltools_0.5.8.1-1
r-cran-httpuv_1.6.15+dfsg-1
r-cran-hunspell_3.0.5+dfsg-1
r-cran-influencer_0.1.5-1
r-cran-interp_1.1-6-1
r-cran-ipred_0.9-15-1
r-cran-irace_4.2.0-1
r-cran-isoband_0.2.7-1
r-cran-isospecr_2.1.3-1
r-cran-jinjar_0.3.2+dfsg-1
r-cran-jomo_2.7-6-1
r-cran-jsonlite_1.9.1+dfsg-1
r-cran-keyring_1.3.2-1
r-cran-knn.covertree_1.0-2
r-cran-ks_1.14.3-1
r-cran-lamw_2.2.4-1
r-cran-later_1.4.1+dfsg-1
r-cran-lavasearch2_2.0.3+dfsg-1
r-cran-lazyeval_0.2.2-1
r-cran-leidenbase_0.1.32-1
r-cran-lexrankr_0.5.2-8
r-cran-lhs_1.2.0-1
r-cran-libcoin_1.0-10-1
r-cran-lobstr_1.1.2-1
r-cran-locfit_1.5-9.12-1
r-cran-lubridate_1.9.4+dfsg-1
r-cran-luminescence_1.0.1-1
r-cran-magick_2.8.5+dfsg-1
r-cran-magrittr_2.0.3-1
r-cran-maldiquant_1.22.3-1
r-cran-maotai_0.2.6-1
r-cran-maps_3.4.2.1-1
r-cran-marginaleffects_0.25.0-1
r-cran-markovchain_0.10.0-1
r-cran-matching_4.10-15-1
r-cran-matchit_4.7.1-1
r-cran-matrixstats_1.5.0-1
r-cran-maxstat_0.7-25-2
r-cran-mclust_6.1.1-1
r-cran-mcmc_0.9-8-1
r-cran-mda_0.5-5-1
r-cran-memisc_0.99.31.8.2+dfsg-1
r-cran-mets_1.3.5+dfsg-1
r-cran-mice_3.17.0-1
r-cran-minerva_1.5.10-1
r-cran-minpack.lm_1.2-4-1
r-cran-mixsqp_0.3-54-1
r-cran-mlbench_2.1-6-1
r-cran-mlr_2.19.2+dfsg-1
r-cran-mnp_3.1-5-1
r-cran-modelmetrics_1.2.2.2-1
r-cran-msm_1.8.2-1
r-cran-mvnfast_0.2.8+dfsg-1
r-cran-nanoarrow_0.6.0-1
r-cran-network_1.19.0-1
r-cran-nmf_0.28-1
r-cran-nnls_1.6-1
r-cran-oaqc_2.0.0-1
r-cran-openmx_2.21.13+dfsg-1
r-cran-openssl_2.3.2+dfsg-1
r-cran-ordinal_2023.12-4.1-1
r-cran-pan_1.9-1
r-cran-pander_0.6.6+dfsg-1
r-cran-parallelly_1.42.0-1
r-cran-paramhelpers_1.14.2-1
r-cran-party_1.3-18-1
r-cran-partykit_1.2-23-1
r-cran-pcapp_2.0-5-1
r-cran-pcict_0.5-4.4-1
r-cran-pdftools_3.5.0-1
r-cran-pec_2023.04.12-1
r-cran-phangorn_2.12.1+dfsg-1
r-cran-phylobase_0.8.12-1
r-cran-pingr_2.0.5-1
r-cran-plyr_1.8.9-1
r-cran-poissonbinomial_1.2.7-1
r-cran-polycub_0.9.2-1
r-cran-princurve_2.1.6-1
r-cran-proc_1.18.5-1
r-cran-processx_3.8.6-1
r-cran-profvis_0.4.0+dfsg-1
r-cran-projpred_2.8.0+dfsg-1
r-cran-promises_1.3.2+dfsg-1
r-cran-prophet_1.0+dfsg-5
r-cran-proxy_0.4-27-1
r-cran-ps_1.9.0-1
r-cran-pscl_1.5.9-1
r-cran-psychotools_0.7-4-1
r-cran-purrr_1.0.4-1
r-cran-purrrlyr_0.0.8-1
r-cran-qap_0.1-2-1
r-cran-qgam_1.3.4-1
r-cran-qgraph_1.9.8-2
r-cran-qpdf_1.3.4+dfsg-2
r-cran-qqconf_1.3.2+dfsg-1
r-cran-qtl_1.70-1
r-cran-quickjsr_1.6.0-1
r-cran-ragg_1.3.3-1
r-cran-randomforest_4.7-1.2-1
r-cran-ranger_0.17.0-1
r-cran-rann_2.6.2-1
r-cran-rappdirs_0.3.3-1
r-cran-rbibutils_2.3-1
r-cran-rcppannoy_0.0.22-1
r-cran-rcppdist_0.1.1-2
r-cran-rcpphnsw_0.6.0+ds-1
r-cran-rcppml_0.3.7-2
r-cran-rcppparallel_5.1.7+dfsg-6
r-cran-rcpproll_0.3.1-1
r-cran-rcpptoml_0.2.3+dfsg-1
r-cran-rcurl_1.98-1.16+dfsg-1
r-cran-redland_1.0.17-18-1
r-cran-regsem_1.9.5+dfsg-1
r-cran-renv_1.1.2-1
r-cran-reshape2_1.4.4-2
r-cran-restfulr_0.0.15-1
r-cran-reticulate_1.41.0.1+dfsg-1
r-cran-rgenoud_5.9-0.11-1
r-cran-riskregression_2023.12.21+ds-1
r-cran-rjson_0.2.23-1
r-cran-rlang_1.1.5-3
r-cran-rle_0.9.2-2
r-cran-rmariadb_1.3.3+ds-1
r-cran-rmpfr_1.0-0-2
r-cran-rncl_0.8.7-1
r-cran-rnetcdf_2.9-2-1
r-cran-roxygen2_7.3.2-1
r-cran-rpact_4.2.0-1
r-cran-rpf_1.0.14+dfsg-1
r-cran-rprotobuf_0.4.23-1
r-cran-rrcov_1.7-6-1
r-cran-rspectra_0.16-2-1
r-cran-rsqlite_2.3.9-1
r-cran-rstan_2.32.7-1
r-cran-rstanarm_2.32.1-2
r-cran-rsvg_2.6.1-1
r-cran-rtdists_0.11-5-1
r-cran-rtsne_0.17-1
r-cran-rwiener_1.3-3-1
r-cran-s7_0.2.0-1
r-cran-samr_3.0-2
r-cran-sass_0.4.9+dfsg-1
r-cran-satellite_1.0.5+dfsg-1
r-cran-scattermore_1.2-1
r-cran-sctransform_0.4.1-1
r-cran-sem_3.1.16-1
r-cran-seriation_1.5.7-1
r-cran-sets_1.0.25+ds-1
r-cran-seurat_5.2.1-5
r-cran-seuratobject_5.0.2-1
r-cran-sitmo_2.0.2-1
r-cran-slider_0.3.2-1
r-cran-sna_2.8-1
r-cran-sodium_1.4.0+dfsg-1
r-cran-sourcetools_0.1.7-1-1
r-cran-sp_1:2.2-0+dfsg-1
r-cran-spam_2.11-1-1
r-cran-sparsevctrs_0.2.0-2
r-cran-spatialreg_1.3-6+dfsg-1
r-cran-spatstat.explore_3.3-4-1
r-cran-spatstat.geom_3.3-6-1
r-cran-spatstat.linnet_3.2-5-1
r-cran-spatstat.model_3.3-4-1
r-cran-spatstat.random_3.3-3-1
r-cran-spatstat.utils_3.1-3-1
r-cran-spdep_1.3-5+dfsg-1
r-cran-splines2_0.5.4-1
r-cran-stanheaders_2.32.10-1
r-cran-statip_0.2.3-2
r-cran-statmod_1.5.0-1
r-cran-statnet.common_4.11.0-1
r-cran-stringdist_0.9.15-1
r-cran-surveillance_1.24.1-1
r-cran-survey_4.4-2-2
r-cran-svglite_2.1.3-2
r-cran-sys_3.4.3-1
r-cran-systemfonts_1.2.1-1
r-cran-testthat_3.2.3-1
r-cran-textshaping_0.3.7-2
r-cran-tfmpvalue_0.0.9-1
r-cran-tgp_2.4-23-1
r-cran-tibble_3.2.1+dfsg-3
r-cran-tidygraph_1.3.1-2
r-cran-tidyr_1.3.1-1
r-cran-tidyselect_1.2.1+dfsg-1
r-cran-tikzdevice_0.12.6-1
r-cran-timechange_0.3.0-2
r-cran-timereg_2.0.6-1
r-cran-tm_0.7-16-1
r-cran-tmvtnorm_1.6-1
r-cran-tokenizers_0.3.0-1
r-cran-transformr_0.1.5-1
r-cran-treespace_1.1.4.3+dfsg-1
r-cran-triebeard_0.4.1-1
r-cran-truncnorm_1.0-9-2
r-cran-tsp_1.2-4-1
r-cran-tweenr_2.0.3-1
r-cran-ucminf_1.2.2-1
r-cran-units_0.8-7+dfsg-2
r-cran-urltools_1.7.3+dfsg-2
r-cran-utf8_1.2.4-1
r-cran-uwot_0.2.3-1
r-cran-vctrs_0.6.5-1
r-cran-vdiffr_1.0.8-1
r-cran-vegan_2.6-10+dfsg-3
r-cran-vgam_1.1-13-1
r-cran-vim_6.2.2+dfsg-1
r-cran-warp_0.2.1-1
r-cran-waveslim_1.8.5-1
r-cran-webfakes_1.3.2-1
r-cran-webutils_1.2.2-1
r-cran-wk_0.9.4-1
r-cran-wordcloud_2.6-2
r-cran-xfun_0.51+dfsg-1
r-cran-xts_0.14.1-1
r-cran-yaml_2.3.10-1
r-other-kcha-psiplot_2.3.0-2
r-other-x4r_1.0.1+git20150806.c6bd9bd-3

Message #10 received at 1121479@bugs.debian.org (full text, mbox, reply):

From: Charles Plessy <plessy@debian.org>

To: Jochen Sprickerhof <jspricke@debian.org>, 1121479@bugs.debian.org

Subject: Re: Bug#1121479: binNMU r-* for reproduce.debian.net

Date: Thu, 27 Nov 2025 18:16:31 +0900

Hi all,

I plan to rebuild all the r-* packages with restricting them to 64-bit little-endian architectures.

Do you think we can coordinate the two mass uploads?

On my side I have been delaying it for a long time because I am under the
impression that the packages must first move out of testing to clear out the
unsupported architectures, and I yet have to find a reasonably minimal set of
packages that I can action to acheive that.

Or shall I just open a RC bug on all of them, and then mass-close the bugs once
the work is done, without changing them in the changelog?  The issue is I do
not have the techical knowledge to make a mass upload of hundred of packages
closing hundreds of different bugs...

Have a nice day,

Charles

Message #15 received at 1121479@bugs.debian.org (full text, mbox, reply):

From: Jochen Sprickerhof <jspricke@debian.org>

To: Charles Plessy <plessy@debian.org>

Cc: 1121479@bugs.debian.org

Subject: Re: Bug#1121479: binNMU r-* for reproduce.debian.net

Date: Thu, 27 Nov 2025 10:32:08 +0100

[Message part 1 (text/plain, inline)]

Hi Charles,

* Charles Plessy <plessy@debian.org> [2025-11-27 18:16]:
>I plan to rebuild all the r-* packages with restricting them to 64-bit little-endian architectures.
>
>Do you think we can coordinate the two mass uploads?

Yes, absolutely.

Btw. could you also do at lest no change uploads of the arch all 
packages listed here:

https://reproduce.debian.net/all/stats/forky/#dpkg-buildpackage-failed:-dh-r-(#1089197)
https://reproduce.debian.net/all/stats/forky/#failed-to-reproduce:-dh-r-(#1089197)

That would help us a lot!

>On my side I have been delaying it for a long time because I am under the
>impression that the packages must first move out of testing to clear out the
>unsupported architectures, and I yet have to find a reasonably minimal set of
>packages that I can action to acheive that.
>
>Or shall I just open a RC bug on all of them, and then mass-close the bugs once
>the work is done, without changing them in the changelog?  The issue is I do
>not have the techical knowledge to make a mass upload of hundred of packages
>closing hundreds of different bugs...

You could simply upload the new packages and fill removal bugs against 
ftp.debian.org afterwards.

Thanks!

Jochen

[signature.asc (application/pgp-signature, inline)]

Message #20 received at 1121479@bugs.debian.org (full text, mbox, reply):

From: Paul Gevers <elbrus@debian.org>

To: Jochen Sprickerhof <jspricke@debian.org>, 1121479@bugs.debian.org, Charles Plessy <plessy@debian.org>

Subject: Re: Bug#1121479: binNMU r-* for reproduce.debian.net

Date: Thu, 27 Nov 2025 12:43:45 +0100

[Message part 1 (text/plain, inline)]

Hi Charles,

On 11/27/25 10:32, Jochen Sprickerhof wrote:
> Hi Charles,
> 
> * Charles Plessy <plessy@debian.org> [2025-11-27 18:16]:
>> I plan to rebuild all the r-* packages with restricting them to 64-bit 
>> little-endian architectures.
>>
>> Do you think we can coordinate the two mass uploads?
> 
> Yes, absolutely.


The request from Jochen and me was about binNMU, which doesn't require 
uploads. Obviously that request becomes moot if your mass upload happens.

> Btw. could you also do at lest no change uploads of the arch all 
> packages listed here:
> 
> https://reproduce.debian.net/all/stats/forky/#dpkg-buildpackage-failed:- 
> dh-r-(#1089197)
> https://reproduce.debian.net/all/stats/forky/#failed-to-reproduce:-dh-r- 
> (#1089197)
> 
> That would help us a lot!


Jochen mentions these as arch:all binaries aren't binNMU-able. However, 
I'd expect they are also not part of your restrict-arch mass upload 
either. So this is an orthogonal request.

>> On my side I have been delaying it for a long time because I am under the
>> impression that the packages must first move out of testing to clear 
>> out the
>> unsupported architectures, and I yet have to find a reasonably minimal 
>> set of
>> packages that I can action to acheive that.

>> Or shall I just open a RC bug on all of them, and then mass-close the 
>> bugs once
>> the work is done, without changing them in the changelog?  The issue 
>> is I do
>> not have the techical knowledge to make a mass upload of hundred of 
>> packages
>> closing hundreds of different bugs...
> 
> You could simply upload the new packages and fill removal bugs against 
> ftp.debian.org afterwards.


With a bit more information, hoping that's useful. Removal from testing 
isn't required as far as I can tell. What need to happen is that 
binaries on the no longer supported architectures need to be removed 
from unstable (by filing RM bugs against ftp.debian.org, they normally 
want one bug per (source) package). I'm not 100% sure, but I think the 
cravat is that you need to prevent the buildds from picking up the build 
again and building new versions of the binary on the architecture you 
just had removed. (I don't think the buildds are smart enough to know 
that the package built in the past for the same version and thus prevent 
building it again). So, if the build doesn't fail or is prevented from 
building currently, you need to fix that first and then have ftp-master 
remove the binaries on those architectures. Once the full set of 
binaries for a particular architecture from a given source is removed in 
unstable and no longer has reverse dependencies in testing, the set will 
be removed from testing too. Although with a new source in unstable I 
think that happens only once the new source migrates too.

So, I think for you mass upload it's probably the easiest to start with 
leaf packages and then work your way up the stack, unless you make 
special arrangements with ftp-master.

Be aware that there are r-* package in the key packages set. If any of 
them is on the list you want to drop 64 bit support for, you'll need to 
take care of the reverse (build) depends first. key packages are hard to 
remove from testing.

Paul

[OpenPGP_signature.asc (application/pgp-signature, attachment)]

Message #25 received at 1121479@bugs.debian.org (full text, mbox, reply):

From: Charles Plessy <plessy@debian.org>

To: Paul Gevers <elbrus@debian.org>

Cc: Jochen Sprickerhof <jspricke@debian.org>, 1121479@bugs.debian.org, Charles Plessy <plessy@debian.org>

Subject: Re: Bug#1121479: binNMU r-* for reproduce.debian.net

Date: Thu, 27 Nov 2025 22:00:04 +0900

Hi Paul,

thanks a lot for the guidance.  Next week I am on business trip but
I will try to start the uploads (including arch all) the week after,
or later if the release team wants me to wait.

>Be aware that there are r-* package in the key packages set.

I am under the impression that only core package maintained by Dirk are
in the key package set and I do not intend to alter them.

But moreover I do not understand why there are R packages in the key
set.  For instance there is r-recommended in the list, which obviously
pulls a bunch of R packages, but there is no key package depending on
r-recommended.  Only one package, cantor, build-depends on r-base-core,
and I do not fully understand why it is in the key package list unless
KDE as a whole is key or something important depends or build-depends on
the capacity to install the kdeedu metapackage, which depends on cantor…

Have a nice day,

Charles

-- 
Charles Plessy                         Nagahama, Yomitan, Okinawa, Japan
Debian Med packaging team         http://www.debian.org/devel/debian-med
Tooting from work,               https://fediscience.org/@charles_plessy
Tooting from home,                 https://framapiaf.org/@charles_plessy

Message #30 received at 1121479@bugs.debian.org (full text, mbox, reply):

From: Chris Hofstaedtler <zeha@debian.org>

To: Charles Plessy <plessy@debian.org>, 1121479@bugs.debian.org

Cc: Paul Gevers <elbrus@debian.org>, Jochen Sprickerhof <jspricke@debian.org>

Subject: Re: Bug#1121479: binNMU r-* for reproduce.debian.net

Date: Thu, 27 Nov 2025 19:08:10 +0100

On Thu, Nov 27, 2025 at 10:00:04PM +0900, Charles Plessy wrote:
> > Be aware that there are r-* package in the key packages set.
> 
> I am under the impression that only core package maintained by Dirk are
> in the key package set and I do not intend to alter them.
> 
> But moreover I do not understand why there are R packages in the key
> set.

r-% in the key set are:
  r-base
  r-cran-class
  r-cran-mass
  r-cran-nnet
  r-cran-spatial


One chain is:

meta:d-i	=>	debian-edu-install
debian-edu-install	depends	debian-edu-config
debian-edu-config	depends	debian-edu
debian-edu	depends	tasksel
tasksel	depends	meta-kde
meta-kde	depends	cantor
cantor	build-depends	r-base

r-base	depends	r-cran-class
r-base	depends	r-cran-mass
r-base	depends	r-cran-nnet
r-base	depends	r-cran-spatial

Best,
Chris

Message #35 received at 1121479@bugs.debian.org (full text, mbox, reply):

From: Adrian Bunk <bunk@debian.org>

To: Charles Plessy <plessy@debian.org>, 1121479@bugs.debian.org

Subject: Re: Bug#1121479: binNMU r-* for reproduce.debian.net

Date: Thu, 27 Nov 2025 20:18:12 +0200

On Thu, Nov 27, 2025 at 06:16:31PM +0900, Charles Plessy wrote:
> Hi all,
> 
> I plan to rebuild all the r-* packages with restricting them to 64-bit little-endian architectures.
>...

Is there a good reason why this is necessary?

I am asking since it tends to be painful to hardcode architecture lists, 
for example in build and test dependencies if some package ends up using 
R in tests.

Like Haskell has little relevance on most architectures, but then 
you have to hardcode architecture lists in the build dependencies
of packages that use pandoc for a manpage (like flac).

> Have a nice day,
> 
> Charles

cu
Adrian

Message #40 received at 1121479@bugs.debian.org (full text, mbox, reply):

From: Charles Plessy <plessy@debian.org>

To: Adrian Bunk <bunk@debian.org>

Cc: Charles Plessy <plessy@debian.org>, 1121479@bugs.debian.org

Subject: Re: Bug#1121479: binNMU r-* for reproduce.debian.net

Date: Fri, 28 Nov 2025 17:59:23 +0900

> On Thu, Nov 27, 2025 at 06:16:31PM +0900, Charles Plessy wrote:
> > 
> > I plan to rebuild all the r-* packages with restricting them to 64-bit little-endian architectures.

Le Thu, Nov 27, 2025 at 08:18:12PM +0200, Adrian Bunk a écrit :
> 
> Is there a good reason why this is necessary?

Hi Adrian,

for 32-bit support removal, yes, it is necessary: 32-bit support is draining a
significant part of our "quality" (focus) time and of the help we receive from
other DDs, while scientific computing on 32-bit machines is basically dead.

Little-endian removal may be heavy-handed but also there is no upstream support
for these architecture in the R world, and if we would want to push it from
Debian I think that it would be more healthy to 1) do it actively with someone
in charge and not reactively like now, and 2) focus on the R packages that
matter the most first.

In any case, if making a couple of exceptions will make porter life easier,
I will be all for it.

Have a nice week-end,

Charles

-- 
Charles Plessy                         Nagahama, Yomitan, Okinawa, Japan
Debian Med packaging team         http://www.debian.org/devel/debian-med
Tooting from home                  https://framapiaf.org/@charles_plessy
- You  do not have  my permission  to use  this email  to train  an AI -

Message #45 received at 1121479@bugs.debian.org (full text, mbox, reply):

From: Holger Levsen <holger@layer-acht.org>

To: Chris Hofstaedtler <zeha@debian.org>, 1121479@bugs.debian.org

Cc: Charles Plessy <plessy@debian.org>, Paul Gevers <elbrus@debian.org>, Jochen Sprickerhof <jspricke@debian.org>

Subject: Re: Bug#1121479: binNMU r-* for reproduce.debian.net

Date: Fri, 28 Nov 2025 09:27:19 +0000

[Message part 1 (text/plain, inline)]

On Thu, Nov 27, 2025 at 07:08:10PM +0100, Chris Hofstaedtler wrote:
> One chain is:
> meta:d-i	=>	debian-edu-install
> debian-edu-install	depends	debian-edu-config
> debian-edu-config	depends	debian-edu
 
which is a bit ironic, because Debian Edu is basically an amd64 blend.


-- 
cheers,
	Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

Die kleinen Lumpen sperrt man ein, vor den großen zieht man den Hut.

[signature.asc (application/pgp-signature, inline)]

Message #50 received at 1121479@bugs.debian.org (full text, mbox, reply):

From: Chris Hofstaedtler <zeha@debian.org>

To: Holger Levsen <holger@layer-acht.org>, 1121479@bugs.debian.org

Cc: Charles Plessy <plessy@debian.org>, Paul Gevers <elbrus@debian.org>, Jochen Sprickerhof <jspricke@debian.org>

Subject: Re: Bug#1121479: binNMU r-* for reproduce.debian.net

Date: Fri, 28 Nov 2025 22:34:07 +0100

On Fri, Nov 28, 2025 at 09:27:19AM +0000, Holger Levsen wrote:
> On Thu, Nov 27, 2025 at 07:08:10PM +0100, Chris Hofstaedtler wrote:
> > One chain is:
> > meta:d-i	=>	debian-edu-install
> > debian-edu-install	depends	debian-edu-config
> > debian-edu-config	depends	debian-edu
>  
> which is a bit ironic, because Debian Edu is basically an amd64 blend.

Probably just one of many things the key package set does not and 
maybe should not take into account.

Incidentally I looked into either the calculation or the autoremoval 
script today and noticed that "cantor" is marked as allow-remove. 
Maybe the r-* packages do not matter for the key package set, in the 
end.

Chris

Message #55 received at 1121479@bugs.debian.org (full text, mbox, reply):

From: Stéphane Glondu <glondu@debian.org>

To: Adrian Bunk <bunk@debian.org>, 1121479@bugs.debian.org, Charles Plessy <plessy@debian.org>

Subject: Re: Bug#1121479: binNMU r-* for reproduce.debian.net

Date: Wed, 10 Dec 2025 14:32:10 +0100

Hi all,

Le 27/11/2025 à 19:18, Adrian Bunk a écrit :
> I am asking since it tends to be painful to hardcode architecture lists,
> for example in build and test dependencies if some package ends up using
> R in tests.

Cannot the hardcoded archictecture list be avoided with the (virtual) 
packages architecture-is-{little-endian,64-bit}?


Cheers,

-- 
Stéphane

Message #60 received at 1121479@bugs.debian.org (full text, mbox, reply):

From: Adrian Bunk <bunk@debian.org>

To: Stéphane Glondu <glondu@debian.org>, 1121479@bugs.debian.org

Cc: Charles Plessy <plessy@debian.org>

Subject: Re: Bug#1121479: binNMU r-* for reproduce.debian.net

Date: Wed, 10 Dec 2025 16:12:42 +0200

On Wed, Dec 10, 2025 at 02:32:10PM +0100, Stéphane Glondu wrote:
> Hi all,
> 
> Le 27/11/2025 à 19:18, Adrian Bunk a écrit :
> > I am asking since it tends to be painful to hardcode architecture lists,
> > for example in build and test dependencies if some package ends up using
> > R in tests.
> 
> Cannot the hardcoded archictecture list be avoided with the (virtual)
> packages architecture-is-{little-endian,64-bit}?

You cannot use these virtual packages in Architecture.
You cannot use these virtual packages for conditional build dependencies.

For autopkgtest skip-not-installable is the best option to avoid the 
hardcoding.

src:cantor from the key package path in this discussion:
  Source: cantor
  Build-Depends: ...,r-base-core,...
  ...
  Package: cantor-backend-r
  Architecture: any

That's two places where architecture lists will have to be hardcoded
if r-base-core would drop 32-bit support (which might not yet happen
as part of the current change).

> Cheers,

cu
Adrian

Message #65 received at 1121479@bugs.debian.org (full text, mbox, reply):

From: Stéphane Glondu <glondu@debian.org>

To: Adrian Bunk <bunk@debian.org>, 1121479@bugs.debian.org

Cc: Charles Plessy <plessy@debian.org>

Subject: Re: Bug#1121479: binNMU r-* for reproduce.debian.net

Date: Wed, 10 Dec 2025 15:32:30 +0100

Le 10/12/2025 à 15:12, Adrian Bunk a écrit :
>> Cannot the hardcoded archictecture list be avoided with the (virtual)
>> packages architecture-is-{little-endian,64-bit}?
> 
> You cannot use these virtual packages in Architecture.
> You cannot use these virtual packages for conditional build dependencies.
> 
> For autopkgtest skip-not-installable is the best option to avoid the
> hardcoding.
> 
> src:cantor from the key package path in this discussion:
>    Source: cantor
>    Build-Depends: ...,r-base-core,...
>    ...
>    Package: cantor-backend-r
>    Architecture: any
> 
> That's two places where architecture lists will have to be hardcoded
> if r-base-core would drop 32-bit support (which might not yet happen
> as part of the current change).

If cantor is supported only on 64-bit architectures, what prevents 
putting architecture-is-64-bit in Build-Depends? (Sorry if I miss 
something obvious.)


Cheers,

-- 
Stéphane

Message #70 received at 1121479@bugs.debian.org (full text, mbox, reply):

From: Adrian Bunk <bunk@debian.org>

To: Stéphane Glondu <glondu@debian.org>

Cc: 1121479@bugs.debian.org, Charles Plessy <plessy@debian.org>

Subject: Re: Bug#1121479: binNMU r-* for reproduce.debian.net

Date: Wed, 10 Dec 2025 16:50:27 +0200

On Wed, Dec 10, 2025 at 03:32:30PM +0100, Stéphane Glondu wrote:
> Le 10/12/2025 à 15:12, Adrian Bunk a écrit :
> > > Cannot the hardcoded archictecture list be avoided with the (virtual)
> > > packages architecture-is-{little-endian,64-bit}?
> > 
> > You cannot use these virtual packages in Architecture.
> > You cannot use these virtual packages for conditional build dependencies.
> > 
> > For autopkgtest skip-not-installable is the best option to avoid the
> > hardcoding.
> > 
> > src:cantor from the key package path in this discussion:
> >    Source: cantor
> >    Build-Depends: ...,r-base-core,...
> >    ...
> >    Package: cantor-backend-r
> >    Architecture: any
> > 
> > That's two places where architecture lists will have to be hardcoded
> > if r-base-core would drop 32-bit support (which might not yet happen
> > as part of the current change).
> 
> If cantor is supported only on 64-bit architectures, what prevents putting
> architecture-is-64-bit in Build-Depends? (Sorry if I miss something
> obvious.)

cantor itself would continue to be supported on 32-bit architectures,
cantor-backend-r is just one of the backend packages.

> Cheers,

cu
Adrian

Message #75 received at 1121479@bugs.debian.org (full text, mbox, reply):

From: Paul Gevers <elbrus@debian.org>

To: Adrian Bunk <bunk@debian.org>, 1121479@bugs.debian.org, Stéphane Glondu <glondu@debian.org>

Cc: Charles Plessy <plessy@debian.org>

Subject: Re: Bug#1121479: binNMU r-* for reproduce.debian.net

Date: Wed, 10 Dec 2025 23:29:45 +0100

[Message part 1 (text/plain, inline)]

Hi,

On 12/10/25 15:12, Adrian Bunk wrote:
> For autopkgtest skip-not-installable is the best option to avoid the
> hardcoding.


Please don't use skip-not-installable. If tests fail because of missing 
test dependencies, use the (negated form of the) Architecture field. I 
can also hint them through. skip-not-installable is marked deprecated.

https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst

Paul

[OpenPGP_signature.asc (application/pgp-signature, attachment)]

Message #80 received at 1121479@bugs.debian.org (full text, mbox, reply):

From: Charles Plessy <plessy@debian.org>

To: Adrian Bunk <bunk@debian.org>

Cc: Stéphane Glondu <glondu@debian.org>, 1121479@bugs.debian.org, Charles Plessy <plessy@debian.org>

Subject: Re: Bug#1121479: binNMU r-* for reproduce.debian.net

Date: Thu, 11 Dec 2025 08:43:23 +0900

Le Wed, Dec 10, 2025 at 04:12:42PM +0200, Adrian Bunk a écrit :
> 
> That's two places where architecture lists will have to be hardcoded
> if r-base-core would drop 32-bit support (which might not yet happen
> as part of the current change).

Hi Adrian and everybody,

indeed there is no plan to change architecture support in r-base-core, nor in
the r-cran package managed by Dirk, which tend to be more central in the
dependency graph than ours.

I will go ahead with starting uploads that restrict architecture in the
team-maintained r-cran-* (first) and r-bioc-* (later) packages.  If there
are objections I will revert these changes.

In principle this overlaps with all the binNMUs proposed in this thread except
for the packages maintained by Dirk, if any.

Have a nice day,

Charles

-- 
Charles Plessy                         Nagahama, Yomitan, Okinawa, Japan
Debian Med packaging team         http://www.debian.org/devel/debian-med
Tooting from home                  https://framapiaf.org/@charles_plessy
- You  do not have  my permission  to use  this email  to train  an AI -

Send a report that this bug log contains spam.