Hi Johannes,
Am Fri, Jun 30, 2023 at 03:22:19PM +0200 schrieb Johannes Ranke:
> I think option 1 from [1] is the way to go, i.e. make r-base provide a
> graphics API version according to the R changelog, and have the relevant
> packages depend on that graphics API version. How to identify them
Hi all,
pardon me the offence and the noise, but I asked ChatGPT...
--
Me:
In Debian, updates of the r-base package sometimes break backwards
compatibility with a small number of binary packages shipping CRAN
packages, which have in common to use R’s graphic API. We
Hi,
I think option 1 from [1] is the way to go, i.e. make r-base provide a
graphics API version according to the R changelog, and have the relevant
packages depend on that graphics API version. How to identify them was
discussed previously on this list [2]. Using the codesearch and github URLS
Hi Dirk,
Am Thu, Jun 29, 2023 at 05:52:34PM -0500 schrieb Dirk Eddelbuettel:
> This accidentally omitted
>
> library(svglite)
>
> The package loads fine, but like the others will not create a graphics device
> as it was built under the previous R 4.2.* series.
Thanks a lot for your
On 29 June 2023 at 10:22, Dirk Eddelbuettel wrote:
|
| Package: r-cran-svglite
| Version: 2.1.1-1
| Severity: normal
|
| R 4.3.0 brought (once again) a new graphics API which requires a rebuild for
| functionality that involves creating graphics device. Once rebuilt the
| following will again
Package: r-cran-svglite
Version: 2.1.1-1
Severity: normal
R 4.3.0 brought (once again) a new graphics API which requires a rebuild for
functionality that involves creating graphics device. Once rebuilt the
following will again work:
> getRversion()
[1] ‘4.3.1’
>
6 matches
Mail list logo