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.
