Am Thu, Jan 02, 2025 at 01:07:05PM -0100 schrieb Graham Inggs:
> Control: affects -1 + src:r-cran-lwgeom
>
> It seems at least r-cran-lwgeom needs updating to 0.2-14 for
> compatibility with the new r-cran-sf [1].
>
> version 0.2-14
>
> st_perimeter() is deprecated in favor of st_perimeter_lwgeo
Control: affects -1 + src:r-cran-lwgeom
It seems at least r-cran-lwgeom needs updating to 0.2-14 for
compatibility with the new r-cran-sf [1].
version 0.2-14
st_perimeter() is deprecated in favor of st_perimeter_lwgeom(), as sf
takes over with sf::st_perimeter().
[1] https://cran.r-project.org
Control: reopen -1
This is not yet solved. The autopkgtests are still failing in testing [1].
[1] https://ci.debian.net/packages/r/r-cran-sf/testing/amd64/
104s Some packages could not be installed. This may mean that you have
104s requested an impossible situation or if you are using the uns
Control: block -1 by 1071523
The problem is connected to the removal of r-cran-spatstat.core from
testing/unstable. Since r-cran-sf (Test-)Depends r-cran-spatstat.geom
fixing bug #1071523 should be sufficient to let r-cran-sf migrate.
Kind regards
Andreas.
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:/
5 matches
Mail list logo
