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.